git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-svn on MSysGit and why is it (going to be?) unsupported

From
Petr Baudis <pasky@suse.cz>
Date
Aug 6, 2008, 13:51 UTC
Message-ID
<20080806135100.GB10151@machine.or.cz>
In-Reply-To
<alpine.DEB.1.00.0808061436310.9611@pacific.mpi-cbg.de.mpi-cbg.de>
Hi!
On Wed, Aug 06, 2008 at 02:43:51PM +0200, Johannes Schindelin wrote:
Show 12 quoted lines
> On Wed, 6 Aug 2008, Petr Baudis wrote:
> 
> > 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

Yes, that's why added the word "significant". ;-) This seems to be simple module-out-of-sync issue.

Show 18 quoted lines
> 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.

Well, when looking through the tracker earlier today, I actually wanted to mark few dupes, but I did not find out how on the earth I'm supposed to do that. Either the operation is well-hidden in the web interface or I have to have some special rights to do that - in which case, it's no wonder the tracker is deteriorating.

Show 6 quoted lines
> >   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?

Because it is not documented? Or is it? *Searches crlf in git-svn.html bundled with his msysgit* *Looks at Git FAQ* *Looks for release notes in the start menu ... unsuccessfully* *Tries to Google out MSysGit release notes ... unsuccessfully* *Founds MSysGit release notes sitting in Program Files* "git svn is slow or seems to be broken (see discussions on the mailing list)" What is "the" mailing list in MSysGit context?

*Googles out MSysGit Google Group* *Searches git-svn and pages... and pages.*

	http://groups.google.com/group/msysgit/browse_thread/thread/8240da55a76f8c92/30656b448e9f5e74?lnk=gst&q=git-svn#30656b448e9f5e74

Okay. That was really easy to find, wasn't it... Somewhere deep inside, even few mentions of autocrlf can be found.

> 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.

I can of course understand that argument, even though it's a bit sad to see when the issues are apparently either trivial or there is simple workaround available. My trouble was that the _concrete_ reasons for this are buried deep inside long mail threads (or threads on other mailing lists).

> 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.

Not currently, I'm just afraid I *might* have to sometime in the future. ;-)

-- 
				Petr "Pasky" Baudis
The next generation of interesting software will be done
on the Macintosh, not the IBM PC.  -- Bill Gates
Previous: Johannes SchindelinNext: Avery Pennarun
Message 11 of 45 in “git-svn does not seems to work with crlf convertion enabled.”
  1. Alexander LitvinovJul 23, 2008
  2. Johannes SchindelinJul 23, 2008
  3. Alexander LitvinovJul 23, 2008
  4. Johannes SchindelinJul 23, 2008
  5. Avery PennarunJul 23, 2008
  6. Johannes SchindelinJul 23, 2008
  7. Alexander LitvinovJul 24, 2008
  8. Petr BaudisAug 6, 2008
  9. Peter HarrisAug 6, 2008
  10. Johannes SchindelinAug 6, 2008
  11. git-svn on MSysGit and why is it (going to be?) unsupportedPetr Baudis, Aug 6, 2008
  12. Avery PennarunAug 6, 2008
  13. Dmitry PotapovAug 6, 2008
  14. Dmitry PotapovJul 24, 2008
  15. Johannes SchindelinJul 24, 2008
  16. Avery PennarunJul 24, 2008
  17. Alexander LitvinovJul 30, 2008
  18. git-svn now work with crlf convertion enabled.Alexander Litvinov, Jul 31, 2008
  19. Alexander LitvinovJul 31, 2008
  20. Dmitry PotapovJul 31, 2008
  21. [RFC] hash-object --no-filtersDmitry Potapov, Jul 31, 2008
  22. Alexander LitvinovAug 1, 2008
  23. Junio C HamanoAug 1, 2008
  24. Dmitry PotapovAug 1, 2008
  25. Alexander LitvinovAug 1, 2008
  26. Dmitry PotapovAug 1, 2008
  27. Junio C HamanoAug 1, 2008
  28. Dmitry PotapovAug 1, 2008
  29. Junio C HamanoAug 1, 2008
  30. Dmitry PotapovAug 1, 2008
  31. Junio C HamanoAug 1, 2008
  32. Dmitry PotapovAug 1, 2008
  33. Junio C HamanoAug 2, 2008
  34. Dmitry PotapovAug 3, 2008
  35. Dmitry PotapovAug 3, 2008
  36. 1/5 correct argument checking test for git hash-objectDmitry Potapov, Aug 3, 2008
  37. 2/5 correct usage help string for git-hash-objectDmitry Potapov, Aug 3, 2008
  38. 3/5 use parse_options() in git hash-objectDmitry Potapov, Aug 3, 2008
  39. 4/5 add --path option to git hash-objectDmitry Potapov, Aug 3, 2008
  40. 5/5 add --no-filters option to git hash-objectDmitry Potapov, Aug 3, 2008
  41. Junio C HamanoAug 3, 2008
  42. Alexander LitvinovAug 1, 2008
  43. Dmitry PotapovAug 1, 2008
  44. Alexander LitvinovAug 4, 2008
  45. Eric WongAug 4, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.