From: "C. Michael Pilato" <cmpilato@collab.net>
To: Ramkumar Ramachandra <artagnon@gmail.com>,
"dev@subversion.apache.org" <dev@subversion.apache.org>,
Bert Huijben <rhuijben@collab.net>,
Daniel Shahaf <d.s@daniel.shahaf.name>,
Will P
Subject: Re: [PATCH v2] Add svnrdump
Date: Wed, 14 Jul 2010 13:31:02 -0400 [thread overview]
Message-ID: <4C3DF456.20803@collab.net> (raw)
In-Reply-To: <20100714172429.GC25861@ted.stsp.name>
On 07/14/2010 01:24 PM, Stefan Sperling wrote:
> On Wed, Jul 14, 2010 at 06:01:49PM +0200, Ramkumar Ramachandra wrote:
>> Yeah, I forgot to ask about this: passing 0 as an argument to the
>> replay API doesn't seem to work. Why? How do I dump revision 0 then?
>
> Indeed. This seems to be a problem in the replay API.
How so? The replay API is for driving an editor with tree changes. There
are by definition no tree changes in revision 0. Therefore, it makes no
sense to accept revision 0 as valid.
Revprops aren't handled by the replay API for any revision.
--
C. Michael Pilato <cmpilato@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
next prev parent reply other threads:[~2010-07-14 17:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 14:29 [PATCH v2] Add svnrdump Ramkumar Ramachandra
2010-07-13 20:11 ` Stefan Sperling
2010-07-14 15:32 ` Stefan Sperling
2010-07-14 16:01 ` Ramkumar Ramachandra
2010-07-14 16:48 ` C. Michael Pilato
2010-07-15 10:28 ` Ramkumar Ramachandra
2010-07-14 17:24 ` Stefan Sperling
2010-07-14 17:31 ` C. Michael Pilato [this message]
2010-07-14 17:34 ` Stefan Sperling
2010-07-14 17:47 ` Jonathan Nieder
2010-07-14 17:56 ` C. Michael Pilato
2010-07-15 12:01 ` Ramkumar Ramachandra
2010-07-14 19:25 ` Bert Huijben
2010-07-15 12:07 ` Ramkumar Ramachandra
2010-07-15 19:02 ` Ramkumar Ramachandra
2010-07-15 19:23 ` Stefan Sperling
2010-07-21 11:46 ` Ramkumar Ramachandra
2010-07-21 13:29 ` Daniel Shahaf
2010-07-21 19:03 ` Ramkumar Ramachandra
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=4C3DF456.20803@collab.net \
--to=cmpilato@collab.net \
--cc=artagnon@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=dev@subversion.apache.org \
--cc=rhuijben@collab.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).