Re: [JGIT PATCH 2/2] Make Repository.isValidRefName compatible with Git 1.6.3

From: Alex Riesen <raa.lkml@gmail.com>
Date: May 8, 2009, 11:45 UTC
Message-ID: <81b0412b0905080445j6d91f05jb13169ebd0245935@mail.gmail.com>
In-Reply-To: <alpine.DEB.1.00.0905081153050.4601@intel-tinevez-2-302>

2009/5/8 Johannes Schindelin <Johannes.Schindelin@gmx.de>:

Show 18 quoted lines

> On Fri, 8 May 2009, Junio C Hamano wrote:
>> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>>
>> >> There must be at least some deprecation period during which also the
>> >> old .lock lockfiles are considered and created. Just imagine someone
>> >> modifying the ref with an older version, which knows nothing about
>> >> ..lck.
>> >
>> > As lock files are only supposed to be created by Git itself, and have
>> > a maximum lifetime until the end of the process, I think we do not
>> > need a grace period at all.
>>
>> Could there be people with slightly older git and shiny new jgit (or the
>> other combination) working on the same repository?
>
> You mean concurrently?  Sure, but do we have to care?  People doing this
> certainly know what they are doing, and live happily even with a 0.5"
> hole in their foot.

I certainly hope that'll be you, one day.

Of course people run git concurrently on the same repo. Even from different machines.

That's _why_ we have the locking in the first place.

And of course there will be different versions of git installed on these machines. And most certainly the people will not know what they were doing, blame the hole on Git (and maybe even shoot you in return, after they'll find that stupid message of yours in archives).