From: Daniel Barkalow <barkalow@iabervon.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/3] Move bundle specific stuff into bundle.[ch]
Date: Tue, 17 Jul 2007 22:48:05 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707172216420.14596@iabervon.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707172346450.14781@racer.site>
On Tue, 17 Jul 2007, Johannes Schindelin wrote:
> The transport specific stuff was moved into libgit.a, and the
> bundle specific stuff will not be left behind.
>
> This is a big code move, with one exception: the function
> unbundle() no longer outputs the list of refs. You have to call
> list_bundle_refs() yourself for that.
You should use -C on this sort of thing, so that the interesting aspects
of the patch are easier to see. (It actually comes out longer in this
case, but it's far easier to tell that the code in the new file is the
same as the old code.) Can you tell I've been rearranging a lot of code
lately and trying to make the patches not look really scary?
Aside from presentation, it looks good to me. Shall I stick the bundle
changes into my series? I'd like to have them come before the patch to
switch to builtin-fetch, so that there aren't any revisions where "git
fetch" doesn't have bundle support.
And I think it would be best to take part 3 as a review fix to my final
patch.
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2007-07-18 2:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 22:49 [PATCH 1/3] Move bundle specific stuff into bundle.[ch] Johannes Schindelin
2007-07-18 2:48 ` Daniel Barkalow [this message]
2007-07-18 3:23 ` Daniel Barkalow
2007-07-18 3:29 ` Shawn O. Pearce
2007-07-18 6:13 ` Junio C Hamano
2007-07-18 6:19 ` Shawn O. Pearce
2007-07-18 7:26 ` Junio C Hamano
2007-07-18 10:09 ` Johannes Schindelin
2007-07-18 9:56 ` Johannes Schindelin
2007-07-18 16:25 ` Daniel Barkalow
2007-07-18 16:33 ` Johannes Schindelin
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=Pine.LNX.4.64.0707172216420.14596@iabervon.org \
--to=barkalow@iabervon.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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).