From: Jonathan Nieder <jrnieder@gmail.com>
To: Eric Wong <normalperson@yhbt.net>
Cc: Nathan Gray <n8gray@n8gray.org>, git@vger.kernel.org
Subject: [PATCH resend 0/2] git-svn: improve documentation of multiple fetch lines
Date: Mon, 13 May 2013 14:30:55 -0700 [thread overview]
Message-ID: <20130513213055.GE3657@google.com> (raw)
In-Reply-To: <20111220012236.GB20979@elie.hsd1.il.comcast.net>
Hi Eric,
I last sent these patches as an RFC a year and a half or so ago[1].
Nathan seemed to like them and they still seem valid, so thought
I'd resubmit. :)
Thoughts of all kinds welcome, as always.
Jonathan Nieder (1):
git-svn: clarify explanation of --destination argument
Nathan Gray (1):
git-svn: multiple fetch/branches/tags keys are supported
Documentation/git-svn.txt | 31 ++++++++++++++++++++++++++-----
1 file changed, 26 insertions(+), 5 deletions(-)
[1] http://thread.gmane.org/gmane.comp.version-control.git/187312/focus=187489
next prev parent reply other threads:[~2013-05-13 21:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 19:51 git-svn: multiple fetch lines Nathan Gray
2011-12-17 10:05 ` Jonathan Nieder
2011-12-19 21:40 ` Nathan Gray
2011-12-20 1:22 ` [RFC/PATCH 0/2] " Jonathan Nieder
2011-12-20 1:23 ` [PATCH 1/2] git-svn: multiple fetch/branches/tags keys are supported Jonathan Nieder
2011-12-20 6:42 ` Nathan Gray
2011-12-20 1:24 ` [PATCH 2/2] git-svn: clarify explanation of --destination argument Jonathan Nieder
2013-05-13 21:30 ` Jonathan Nieder [this message]
2013-05-13 21:31 ` [PATCH 1/2] git-svn: multiple fetch/branches/tags keys are supported Jonathan Nieder
2013-05-13 21:32 ` [PATCH 2/2] git-svn: clarify explanation of --destination argument Jonathan Nieder
2013-05-15 2:00 ` [PATCH resend 0/2] git-svn: improve documentation of multiple fetch lines Eric Wong
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=20130513213055.GE3657@google.com \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=n8gray@n8gray.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.