| commit | cab6346d07be8f44ea38f289f7b441ccf69f048d | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Wed, 2 Apr 2008 02:22:28 +0000 (1 22:22 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Mon, 7 Apr 2008 05:06:42 +0000 (7 01:06 -0400) | ||
| tree | c0fe741f0fa3ced15fca0b4963cf2e5498bfe17d | treesnapshot (tar.gz zip) |
| parent | 18ca1483ea74e7ccbe817b0515b0fabd3de9e424 | commitdiff |
Rename RefLock to LockFile as its a generic locking system
This locking strategy is suitable for a lot more formats than just
refs. In C Git it gets used for the dircache (aka .git/index), for
a symbolic ref (aka .git/HEAD) and also for the packed-refs file.
Consequently it is a very commonly employed strategy that we also
need to use throughout jgit to remain as compatible as possible with
C Git and its on disk repository format.
To aid confusion our LockFile depends upon java.nio.channels.FileLock.
This is something we inherited from RefLock and its desire to use the
platform locking strategy available from the JRE.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
This locking strategy is suitable for a lot more formats than just
refs. In C Git it gets used for the dircache (aka .git/index), for
a symbolic ref (aka .git/HEAD) and also for the packed-refs file.
Consequently it is a very commonly employed strategy that we also
need to use throughout jgit to remain as compatible as possible with
C Git and its on disk repository format.
To aid confusion our LockFile depends upon java.nio.channels.FileLock.
This is something we inherited from RefLock and its desire to use the
platform locking strategy available from the JRE.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>