From: Jonathan Nieder <jrnieder@gmail.com>
To: David Barr <davidbarr@google.com>
Cc: Scott Chacon <schacon@gmail.com>,
Brian Gernhardt <benji@silverinsanity.com>,
david@lang.hm, Ramkumar Ramachandra <artagnon@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Dmitry Ivankov <divanorama@gmail.com>
Subject: Re: [linux.conf.au] VCS Interoperability
Date: Thu, 26 Jan 2012 18:10:41 -0600 [thread overview]
Message-ID: <20120127001041.GB6158@burratino> (raw)
In-Reply-To: <CAFfmPPPvpbsYz9cjN6OspivCN3dbuPGOU7fyaVdnic3D4V855w@mail.gmail.com>
Hi,
David Barr wrote:
> After giving my talk, I feel compelled to reroll the historic vcs-svn series.
> I'm pushing as I go to my GitHub account:
>
> https://github.com/barrbrain/git/commits/svn-fe-reroll
Just some quick notes to save some time:
All the commits on the
git://repo.or.cz/git/jrn.git svn-fe
branch were known-good in the sense that they seemed sane enough to
build on and I do not think they need any reorganization or other
work. Maybe that could help bootstrap your efforts?
The svn-fe-pu branch includes some other patches: some optimizations
which are probably safe, the demo helper that allows "git clone
svn-alpha::<url>", some transport-helper patches to support the
latter, and so on. They are not vetted. If anyone sends patches from
that branch, or any other patch for that matter, to the list and cc-s
me, I'll be happy to review them. Here's a shortlog for convenience:
David Barr (2):
fast-import: allow object_table to grow dynamically
fast-import: allow atom_table to grow dynamically
Dmitry Ivankov (2):
Arrange a backflow pipe from fast-importer to remote helper stdin
Add alpha version of remote-svn helper
Jonathan Nieder (12):
work around ISO C incompatibility between data and function pointers
ensure initializer elements are computable at load time
enums: omit trailing comma for portability
notes: avoid C99-style comment
notes merge: eliminate OUTPUT macro
make sure initializers are computable at load time
fast-import: allow branch_table to grow dynamically
fast-import: use DIV_ROUND_UP
svn-fe: add a program that generates a notes-to-svn-revs mapping
svn-fe: do not rely on /bin/env utility to launch remote helper
svn-fe: use tabs to indent in remote helper script
remaining warnings
Test results from the svn-fe branch would be interesting. I am
particularly nervous about asking Junio to pull changes to
contrib/svn-fe that might break it at the same time as making the
interface changes needed for support of the "svnadmin dump
--incremental" format without much testing since it would be painful
to back them out. But probably that's moot, since after this long
while there still hasn't been anyone testing it.
Jonathan
next prev parent reply other threads:[~2012-01-27 0:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 12:30 [linux.conf.au] VCS Interoperability David Michael Barr
2012-01-10 8:48 ` Ramkumar Ramachandra
2012-01-22 3:39 ` David Michael Barr
2012-01-22 10:25 ` Ramkumar Ramachandra
2012-01-22 21:12 ` david
2012-01-22 23:33 ` Brian Gernhardt
2012-01-23 0:43 ` Scott Chacon
2012-01-26 23:47 ` David Barr
2012-01-27 0:10 ` Jonathan Nieder [this message]
2012-01-27 0:33 ` [PULL] svn-fe updates for master or next Jonathan Nieder
2012-01-27 0:46 ` Jonathan Nieder
2012-01-27 1:03 ` David Barr
2012-01-27 7:20 ` Jonathan Nieder
2012-01-27 18:39 ` Junio C Hamano
2012-01-28 4:37 ` Junio C Hamano
2012-01-27 18:50 ` Junio C Hamano
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=20120127001041.GB6158@burratino \
--to=jrnieder@gmail.com \
--cc=artagnon@gmail.com \
--cc=benji@silverinsanity.com \
--cc=david@lang.hm \
--cc=davidbarr@google.com \
--cc=divanorama@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=schacon@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).