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

Re: [PATCH] remove noise and inaccuracies from git-svn docs

From
Michael J Gruber <git@drmicha.warpmail.net>
Date
Apr 19, 2011, 11:19 UTC
Message-ID
<4DAD6FC4.6060004@drmicha.warpmail.net>
In-Reply-To
<20110419093108.GA7440@ted.stsp.name>
Stefan Sperling venit, vidit, dixit 19.04.2011 11:31:
Show 31 quoted lines
> On Mon, Apr 18, 2011 at 10:55:18AM -0700, Junio C Hamano wrote:
>> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>>
>>> Stefan Sperling <stsp@stsp.name> writes:
>>>
>>>> -DESIGN PHILOSOPHY
>>>> ------------------
>>>> -Merge tracking in Subversion is lacking and doing branched development
>>>> -with Subversion can be cumbersome as a result.  While 'git svn' can
>>>> track
>>>
>>> Agreed (this and the rest of the patch). Users reading git-svn's doc
>>> don't want a dissertation about how bad SVN is, and if they do, they can
>>> read whygitisbetterthanx ;-)
> 
> Exactly :)
> 
> And they might rather want to learn more about how Subversion has improved
> since version 1.4. It seems that these parts of the text were written
> before Subversion's 1.5 release. SVN is a lot more capable now than the
> git-svn docs suggest and I'm surprised that git-svn's development seems
> to have gotten stuck at the 1.4 level of functionality. Not even CentOS
> ships with 1.4 anymore these days.
> 
> E.g. git-svn could be taught to generate svn mergeinfo compatible with other
> Subversion clients. It's not easy to come up with a generic mapping between
> the two systems but for some use cases it should be reasonably straightforward.
> This would be a nice improvement towards making git-svn a proper drop-in
> replacement for the standard svn client. Currently, git-svn cannot be
> used without disturbing other users doing merges with Subversion itself
> which is a pity.
6abd933 (git-svn: allow the mergeinfo property to be set, 2010-09-24)

made a first step in that direction so that you can at least add mergeinfo manually. But, git-svn.perl is basically in maintenance mode it seems, and more work is being done to implement a new svn remote helper.

Also, I think merge tracking wasn't that reliable in svn 1.5 before svn 1.6, and we try to support older versions. In particular, we want to support the versions on typical svn hosting sites which are not always that recent.

Show 8 quoted lines
> 
> I don't have time to work on this myself but I would be more than happy
> to assist with design and review.
> 
>> I agree the change in the patch is good.  It needs to be signed-off,
>> though.
> 
> I've sent a signed-off version with git send-email. Thanks!
Previous: Stefan SperlingNext: Stefan Sperling
Message 6 of 16 in “remove noise and inaccuracies from git-svn docs”
  1. remove noise and inaccuracies from git-svn docsStefan Sperling, Apr 18, 2011
  2. Matthieu MoyApr 18, 2011
  3. Junio C HamanoApr 18, 2011
  4. remove noise and inaccuracies from git-svn docsStefan Sperling, Apr 19, 2011
  5. Stefan SperlingApr 19, 2011
  6. Michael J GruberApr 19, 2011
  7. Stefan SperlingApr 19, 2011
  8. Michael J GruberApr 19, 2011
  9. Piotr KrukowieckiApr 19, 2011
  10. git-svn and a new svn remote helperMatthew L Daniel, May 5, 2011
  11. Sverre RabbelierMay 5, 2011
  12. Matthew DanielMay 5, 2011
  13. Sverre RabbelierMay 5, 2011
  14. Stefan SperlingApr 28, 2011
  15. Michael SchubertApr 28, 2011
  16. Stefan SperlingApr 29, 2011

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.