All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Andrew Sayers <andrew-git@pileofstuff.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailing List <git@vger.kernel.org>,
	David Barr <davidbarr@google.com>,
	Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [PATCHv2] Add details about svn-fe's dumpfile parsing
Date: Mon, 16 Apr 2012 16:39:10 -0500	[thread overview]
Message-ID: <20120416213910.GP12613@burratino> (raw)
In-Reply-To: <4F8C909B.7010507@pileofstuff.org>

Andrew Sayers wrote:

> The dumpfile documentation says that "... property key/value pairs may
> be interpreted as binary data in any encoding by client tools"[1], but
> SVN itself interprets the data as UTF-8

Yes, I suspect most of the changes you proposed for the INPUT FORMAT
section would actually be better as changes for the
dump-load-format.txt document.  I imagine that folks on the dev@ list
might be able to clarify a few details (e.g., what one is expected to
do with historical repositories with non-UTF-8 property data), too.
What do you think?

The patch for svn-fe(1) already looks pretty good.  I was planning on
applying it after finding a moment to clarify the patch description.

Thanks again,
Jonathan

  reply	other threads:[~2012-04-16 21:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-15 16:10 [PATCHv2] Add details about svn-fe's dumpfile parsing Andrew Sayers
2012-04-16 20:06 ` Junio C Hamano
2012-04-16 21:35   ` Andrew Sayers
2012-04-16 21:39     ` Jonathan Nieder [this message]
2012-04-16 22:15       ` Andrew Sayers
2012-04-16 22:27         ` Jonathan Nieder
2012-07-23  1:37       ` 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=20120416213910.GP12613@burratino \
    --to=jrnieder@gmail.com \
    --cc=andrew-git@pileofstuff.org \
    --cc=artagnon@gmail.com \
    --cc=davidbarr@google.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.