From: Ramkumar Ramachandra <artagnon@gmail.com>
To: "dev@subversion.apache.org" <dev@subversion.apache.org>,
Bert Huijben <rhuijben@collab.net>,
Daniel Shahaf <d.s@daniel.shahaf.name>,
Will Palmer <wmpalmer@gmail.com>,
David Michael B
Subject: Re: [PATCH v2] Add svnrdump
Date: Thu, 15 Jul 2010 14:01:43 +0200 [thread overview]
Message-ID: <20100715120143.GE22574@debian> (raw)
In-Reply-To: <20100714172429.GC25861@ted.stsp.name>
Hi Stefan,
Stefan Sperling writes:
> > This isn't in the dump-load-format spec document (atleast afaik), and
> > it's very hard to get this right (yes, I tried). Moreover, it's very
> > ungratifying to have a few extra newlines (reverse engineered from
> > `svnadmin dump`) printed at the end of 10+ hrs of work; yes, that's
> > what I estimate it'll take to fix this.
>
> Well, it would be really nice to have.
> Details like this are time sinks, I know. But it pays off.
> You don't have to do it right away. We can file an issue so we don't
> forget about fixing it before 1.7 release.
> If necessary, feel free to adjust the output of svnadmin dump a little
> if that makes it easier for svnrdump to produce matching output.
I think the latter is certainly an option. We definitely need to fix
the dump-load-format spec to show everything.
> > gawk '$0 !~ "Prop-delta: true|Text-delta-base-|sha1|Text-copy-source-|^-$" && $0 ~ "^+|^-" { print; }'
>
> Fine for testing. But I still think the end-result should look just
> like svnadmin dump, if possible. That would make testing even easier.
Right. We can use the same test suite and maintenance would become
infinitely easier.
> > > Please get rid of all global variables in svnrdump.c:
> > Will do. I'm waiting for commit access, because I don't want to make
> > un-versioned edits to the file that I cannot track or revert in
> > future.
>
> What about using git until then? It does not matter which state you
> initially import into the Subversion repository. But well, whatever
> works for you is best.
Oh, I didn't think it would take this long for my account to get
activated. I'll consider using Git to stage for now because I don't
want to delay the response to your review.
-- Ram
next prev parent reply other threads:[~2010-07-15 12:00 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
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 [this message]
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=20100715120143.GE22574@debian \
--to=artagnon@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=dev@subversion.apache.org \
--cc=rhuijben@collab.net \
--cc=wmpalmer@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 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).