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

[PATCH] Documentation/git-svn: updated design philosophy notes

From
EWEric Wong <normalperson@yhbt.net>
Date
Sep 18, 2007, 23:50 UTC
Message-ID
<20070918235042.GA11992@untitled>

This section has not been updated in a while and --branches/--tags/--trunk options are commonly used nowadays.

Noticed-by: Lars Hjemli <hjemli@gmail.com>
Signed-off-by: Eric Wong <normalperson@yhbt.net>
---
 Documentation/git-svn.txt |   11 ++++++-----
 1 files changed, 6 insertions(+), 5 deletions(-)
  Eric Wong <normalperson@yhbt.net> wrote:
  > Lars Hjemli <hjemli@gmail.com> wrote:
  > > When updating git-svn.txt, I noticed that we might want to update the
  > > section "DESIGN PHILOSOPHY". Eric?
  > 
  > Yeah.  That's very much out of date.  I'll update it in a bit.
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index be2e34e..e157c6a 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -478,11 +478,12 @@ previous commits in SVN.
 DESIGN PHILOSOPHY
 -----------------
 Merge tracking in Subversion is lacking and doing branched development
-with Subversion is cumbersome as a result.  git-svn does not do
-automated merge/branch tracking by default and leaves it entirely up to
-the user on the git side.  git-svn does however follow copy
-history of the directory that it is tracking, however (much like
-how 'svn log' works).
+with Subversion can be cumbersome as a result.  While git-svn can track
+copy history (including branches and tags) for repositories adopting a
+standard layout, it cannot yet represent merge history that happened
+inside git back upstream to SVN users.  Therefore it is advised that
+users keep history as linear as possible inside git to ease
+compatibility with SVN (see the CAVEATS section below).
 
 CAVEATS
 -------
-- 
Eric Wong
Message 1 of 1 in “Documentation/git-svn: updated design philosophy notes”
  1. Documentation/git-svn: updated design philosophy notesEric Wong, Sep 18, 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.