Re: non-US-ASCII file names (e.g. Hiragana) on Windows
- From
Shawn Pearce <spearce@spearce.org>
- Date
- Dec 2, 2009, 16:22 UTC
- Message-ID
- <ec874dac0912020822t58477e12y3e6d1ab37da4f7e5@mail.gmail.com>
- In-Reply-To
- <4B15668A.5050209@syntevo.com>
On Tue, Dec 1, 2009 at 10:55 AM, Thomas Singer <thomas.singer@syntevo.com> wrote:
Show 12 quoted lines
> > Jakub Narebski wrote: > > If you use Git from Java, why don't you just use JGit (www.jgit.org), > > which is Git implementation in Java? > > We are using JGit for the read-only stuff and the Git command line > executable for all writing commands. We very much appreciate Shawn O. > Pearce' (and the other JGit developers') effort, but Git is a fast moving > target and (much) more complex than CVS or SVN, for which we use Java > libraries communicating with the corresponding server which adds another > sanity layer to the repository making repository corruption less likely than > direct access.
Uhm. I'm sorry, but this is just plain FUD.
JGit implements the current on disk formats and network protocols completely[1]. In the area of disk formats and network protocols, Git *IS NOT* a fast moving target. This area of Git hasn't changed much since pack files were first introduced. As a community, we have been very careful to avoid changes which break compatibility with older implementations.
Git is also a lot less complex than CVS or SVN. Its data model is simpler on disk. Its network protocol is *vastly* more simple than SVN's WebDAV protocol. And unlike SVN we haven't had to break the network protocol on every 1.x release we make.
[1] Actually, JGit lacks --depth support for shallow clones, but otherwise is complete.