projects / git.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 49295d4) | patch
Do not allow ".lock" at the end of any refname component
authorMichael Haggerty <mhagger@alum.mit.edu>
Thu, 15 Sep 2011 21:10:27 +0000 (23:10 +0200)
committerJunio C Hamano <gitster@pobox.com>
Wed, 5 Oct 2011 20:45:30 +0000 (13:45 -0700)
commit7e9d2fe96060957d90870d2fac9b85608423e277
treedc68fe7286d63488a9a9a0115554b7ac75a16e41tree | snapshot
parent49295d4e3fb58c6179b7434cd87805f86cb1f7b7commit | diff
Do not allow ".lock" at the end of any refname component

Allowing any refname component to end with ".lock" is looking for
trouble; for example,

    $ git br foo.lock/bar
    $ git br foo
    fatal: Unable to create '[...]/.git/refs/heads/foo.lock': File exists.

Therefore, do not allow any refname component to end with ".lock".

Signed-off-by: Michael Haggerty <mhagger@alum.mit.edu>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Documentation/git-check-ref-format.txt diff | blob | history
refs.c diff | blob | history
t/t1402-check-ref-format.sh diff | blob | history
Git—the stupid content tracker