Re: git-svn does not seems to work with crlf convertion enabled.
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Aug 6, 2008, 12:43 UTC
- Message-ID
- <alpine.DEB.1.00.0808061436310.9611@pacific.mpi-cbg.de.mpi-cbg.de>
- In-Reply-To
- <20080806111545.GD32184@machine.or.cz>
Hi,
On Wed, 6 Aug 2008, Petr Baudis wrote:
Show 8 quoted lines
> On Wed, Jul 23, 2008 at 01:57:54PM +0100, Johannes Schindelin wrote: > > Note that you will have to do your digging using msysGit (i.e. the > > developer's pack, not the installer for plain Git), since git-svn will > > be removed from the next official "Windows Git" release, due to lack > > of fixers. > > is there any other problem with git-svn on Windows than the CRLF > issue? I couldn't find anything significant in the issue tracker.
http://code.google.com/p/msysgit/issues/detail?id=120&colspec=ID%20Type%20Status%20Priority%20Component%20Owner%20Summary
It is also frustrating that
http://code.google.com/p/msysgit/issues/detail?id=83&colspec=ID%20Type%20Status%20Priority%20Component%20Owner%20Summary http://code.google.com/p/msysgit/issues/detail?id=103&colspec=ID%20Type%20Status%20Priority%20Component%20Owner%20Summary http://code.google.com/p/msysgit/issues/detail?id=129&colspec=ID%20Type%20Status%20Priority%20Component%20Owner%20Summary
are probably the same issue. I cannot only blame the users for not really looking if their issue has been reported yet; there are 32 open issues in msysGit right now, number increasing, so it gets quite confusing.
I once switched off the issue tracker, because I was the only one who took at least a little bit of care of it. Due to list consensus, it was turned back on -- against my will.
Guess who takes care of it right now?
Exactly. So I will soon be switching it off again, I think, because there are few more useless things than an unmonitored issue tracker.
> If not, why do you want to drop git-svn from Windows Git? It seems > that the CRLF issue has trivial workaround to set autocrlf=false; this > will make git-svn-tracked repositories useful only on Windows, but I'd > bet this is fine for large majority of Windows git-svn users?
If it was so trivial, why does nobody use it?
Oh, and git-svn is slow, too.
And _noone_ of those competent Windows git-svn users seemed fit or willing to do anything about git-svn, not even the simplest of issues.
If you want to do something about it, go ahead. But I have no inclination of hearing from any Windows user about git-svn again, ever.
Ciao, Dscho