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

Re: [PATCH] git-svn: update documentation with CAVEATS section

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 22, 2007, 22:41 UTC
Message-ID
<7v4piri44r.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20070816085645.GA3159@soma>
Eric Wong <normalperson@yhbt.net> writes:
Show 17 quoted lines
>   I've been meaning to do this for a while, hopefully this cuts
>   down on the redundant mailing list traffic about these subjects.
> ...
> +CAVEATS
> +-------
> +
> +For the sake of simplicity and interoperating with a less-capable system
> +(SVN), it is recommended that all git-svn users clone, fetch and dcommit
> +directly from the SVN server, and avoid all git-clone/pull/merge/push
> +operations between git repositories and branches.  The recommended
> +method of exchanging code between git branches and users is
> +git-format-patch and git-am, or just dcommiting to the SVN repository.
> +
> +Running 'git-merge' or 'git-pull' is NOT recommended on a branch you
> +plan to dcommit from.  Subversion does not represent merges in any
> +reasonable or useful fashion; so users using Subversion cannot see any
> +merges you've made.

Ok, my ruling before 1.5.3 is to take this patch, and encourage interested parties to help Eric adding reliable support for the feature after that, if such is possible.

Previous: Eric WongNext: David Kastrup
Message 2 of 7 in “git-svn: update documentation with CAVEATS section”
  1. git-svn: update documentation with CAVEATS sectionEric Wong, Aug 16, 2007
  2. Junio C HamanoAug 22, 2007
  3. David KastrupAug 22, 2007
  4. Eric WongAug 23, 2007
  5. David KastrupAug 23, 2007
  6. Eric WongAug 23, 2007
  7. David KastrupAug 23, 2007

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.