From: Andrew Sayers <andrew-git@pileofstuff.org>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
David Barr <davidbarr@google.com>,
Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [PATCH] Explain how svn-fe parses filenames in SVN dumps
Date: Sat, 14 Apr 2012 22:56:11 +0100 [thread overview]
Message-ID: <4F89F27B.5050706@pileofstuff.org> (raw)
In-Reply-To: <20120414181823.GB4560@burratino>
On 14/04/12 19:18, Jonathan Nieder wrote:
> So as far as I can tell the story really is only about newlines. (If
> svn-fe tried to push history back to Subversion, life would presumably
> be more complicated.)
I think I've been trying to balance two incompatible use cases -
ordinary users that just need a heads-up about a bug that might bite
them, and authors of related tools (i.e. me) that need technical
information about svn-fe.
I think your text serves ordinary users better, so I'll investigate
pushing history back to Subversion tomorrow and think how to write
something more technical. I'm afraid my patch etiquette fails me here
though - is it better for me to roll your text into a new patch, or let
you do that and submit my text separately?
- Andrew
next prev parent reply other threads:[~2012-04-14 21:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-14 17:03 [PATCH] Explain how svn-fe parses filenames in SVN dumps Andrew Sayers
2012-04-14 17:14 ` Jonathan Nieder
2012-04-14 17:37 ` Andrew Sayers
2012-04-14 18:13 ` Jonathan Nieder
2012-04-14 18:18 ` Jonathan Nieder
2012-04-14 21:56 ` Andrew Sayers [this message]
2012-04-15 5:08 ` Jonathan Nieder
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=4F89F27B.5050706@pileofstuff.org \
--to=andrew-git@pileofstuff.org \
--cc=artagnon@gmail.com \
--cc=davidbarr@google.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/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.