From: Ramkumar Ramachandra <artagnon@gmail.com>
To: David Michael Barr <david.barr@cordelta.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [GSoC update] git-remote-svn: Week 1
Date: Mon, 10 May 2010 10:29:40 +0200 [thread overview]
Message-ID: <i2gf3271551005100129s63b14129r5207cd177881c3ba@mail.gmail.com> (raw)
In-Reply-To: <66B5CC1B-044A-483E-88D2-DCB0785E3ABE@cordelta.com>
Hi David,
On Mon, May 10, 2010 at 9:08 AM, David Michael Barr
<david.barr@cordelta.com> wrote:
> I was working on a slow but reliable alternate implementation for
> validation and regression testing. So far, it seems really hard to write
> anything reliable atop Subversion.
Okay. I won't really touch that because I'm not very fluent in Perl.
> I know its bad form, but I've done what I promise is the last history
> manipulation on my public repository. Now that the code is at a point
> that is quite functional and ready to receive contributions, I've signed
> off on my own commits and reviewed the history.
On a related note, we might also want to benchmark it against
alternatives and make the benchmarks public for the 1.0 release.
> On that note, do you think I should rewrite my history to include
> 'signed-off' or any other cleanup before I start accepting patches?
Yeah, I don't think we should have a problem with non-FF updates,
atleast until the project reaches 1.0 and becomes more public.
-- Ram
prev parent reply other threads:[~2010-05-10 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 12:59 [GSoC update] git-remote-svn: Week 1 Ramkumar Ramachandra
2010-05-05 20:56 ` David Michael Barr
2010-05-09 22:12 ` Ramkumar Ramachandra
2010-05-10 7:08 ` David Michael Barr
2010-05-10 8:29 ` Ramkumar Ramachandra [this message]
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=i2gf3271551005100129s63b14129r5207cd177881c3ba@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=david.barr@cordelta.com \
--cc=git@vger.kernel.org \
--cc=srabbelier@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).