From: Jonathan Nieder <jrnieder@gmail.com>
To: Andrew Sayers <andrew-git@pileofstuff.org>
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 13:18:23 -0500 [thread overview]
Message-ID: <20120414181823.GB4560@burratino> (raw)
In-Reply-To: <4F89B5C5.3030606@pileofstuff.org>
Andrew Sayers wrote:
> For example, the handling of NUL characters is worse
> than newlines
Filenames are C strings. Filenames with NUL bytes simply do not
exist, at least as long as one is using the ANSI C or POSIX interfaces
for file access.
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.)
Hoping that clarifies a little,
Jonathan
next prev parent reply other threads:[~2012-04-14 18:18 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 [this message]
2012-04-14 21:56 ` Andrew Sayers
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=20120414181823.GB4560@burratino \
--to=jrnieder@gmail.com \
--cc=andrew-git@pileofstuff.org \
--cc=artagnon@gmail.com \
--cc=davidbarr@google.com \
--cc=git@vger.kernel.org \
/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).