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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Fri, 8 May 2009, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@xxxxxx> 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.

Ciao,
Dscho

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]