From: Junio C Hamano <gitster@pobox.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-svn: update documentation with CAVEATS section
Date: Wed, 22 Aug 2007 15:41:24 -0700 [thread overview]
Message-ID: <7v4piri44r.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20070816085645.GA3159@soma> (Eric Wong's message of "Thu, 16 Aug 2007 01:56:45 -0700")
Eric Wong <normalperson@yhbt.net> writes:
> 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.
next prev parent reply other threads:[~2007-08-22 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 8:56 [PATCH] git-svn: update documentation with CAVEATS section Eric Wong
2007-08-22 22:41 ` Junio C Hamano [this message]
2007-08-22 22:51 ` David Kastrup
2007-08-23 5:30 ` Eric Wong
2007-08-23 6:00 ` David Kastrup
2007-08-23 6:26 ` Eric Wong
2007-08-23 7:48 ` David Kastrup
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v4piri44r.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).