From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Michael G. Schwern" <schwern@pobox.com>,
git@vger.kernel.org, robbat2@gentoo.org,
bwalton@artsci.utoronto.ca, normalperson@yhbt.net
Subject: Re: [PATCH 4/4] Move initialization of Git::SVN variables into Git::SVN.
Date: Fri, 27 Jul 2012 00:38:00 -0500 [thread overview]
Message-ID: <20120727053800.GC4685@burratino> (raw)
In-Reply-To: <7vhast3hpb.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> "Michael G. Schwern" <schwern@pobox.com> writes:
>> Also it can compile on its own now, yay!
>
> Hmmm.
I agree with Michael's "yay" and also think it's fine that after
patch 3 it isn't there yet.
That's because git-svn.perl doesn't use Git::SVN on its own but helps
it out a little. So even if we only applied patches 1-3, git-svn
would still work (maybe it's worth testing "perl -MGit::SVN" by hand
to avoid the "it's doubtful" about whether Git::SVN is self-contained
and replace it with a more certain statement?), and patch 4 just makes
it even better.
[...]
> In short:
>
> - I didn't see anything questionable in 1/4;
>
> - Calling up ::opt_prefix() from module in 2/4 looked ugly to me
> but I suspect it should be easy to fix;
>
> - 3/4 was a straight move and I didn't see anything questionable in
> it, but I think it would be nicer if intermediate steps can be
> made to still work by making 4/4 come first or something
> similarly simple.
>
> If the issues in 2/4 and 3/4 are easily fixable by going the route I
> handwaved above, the result of doing so based on this round is ready
> to be applied, I think.
>
> Eric, Jonathan, what do you think?
I think this is pretty good already, though I also like your
suggestion re 2/4.
I haven't reviewed the tests these introduce and assume Eric has that
covered.
Thanks,
Jonathan
next prev parent reply other threads:[~2012-07-27 5:38 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 23:22 Extract Git::SVN from git-svn, take 2 Michael G. Schwern
2012-07-26 23:22 ` [PATCH 1/4] Extract some utilities from git-svn to allow extracting Git::SVN Michael G. Schwern
2012-07-27 5:18 ` Junio C Hamano
2012-07-27 8:19 ` Michael G Schwern
2012-07-27 11:34 ` Eric Wong
2012-07-26 23:22 ` [PATCH 2/4] Prepare Git::SVN for extraction into its own file Michael G. Schwern
2012-07-27 5:18 ` Junio C Hamano
2012-07-27 5:23 ` Junio C Hamano
2012-07-27 8:16 ` Michael G Schwern
2012-07-27 11:53 ` Eric Wong
2012-07-26 23:22 ` [PATCH 4/4] Move initialization of Git::SVN variables into Git::SVN Michael G. Schwern
2012-07-27 5:18 ` Junio C Hamano
2012-07-27 5:38 ` Jonathan Nieder [this message]
2012-07-27 6:07 ` Junio C Hamano
2012-07-27 6:46 ` Junio C Hamano
2012-07-27 7:09 ` Junio C Hamano
2012-07-27 20:07 ` Eric Wong
2012-07-27 20:56 ` Michael G Schwern
2012-07-27 20:59 ` Eric Wong
2012-07-27 21:31 ` Junio C Hamano
2012-07-27 21:49 ` Junio C Hamano
2012-07-27 22:07 ` Eric Wong
2012-07-27 22:19 ` Eric Wong
2012-07-27 22:37 ` Junio C Hamano
2012-07-27 22:45 ` Eric Wong
2012-07-27 22:59 ` Junio C Hamano
2012-07-27 23:01 ` Eric Wong
2012-07-27 22:52 ` Junio C Hamano
2012-07-27 11:59 ` Eric Wong
2012-07-27 8:41 ` Michael G Schwern
-- strict thread matches above, loose matches on Subject: below --
2012-07-25 6:01 Move Git::SVN into its own .pm file Michael G. Schwern
2012-07-25 6:01 ` [PATCH 4/4] Move initialization of Git::SVN variables into Git::SVN Michael G. Schwern
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=20120727053800.GC4685@burratino \
--to=jrnieder@gmail.com \
--cc=bwalton@artsci.utoronto.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=normalperson@yhbt.net \
--cc=robbat2@gentoo.org \
--cc=schwern@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 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).