From: "Kristian Høgsberg" <krh@redhat.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: Post-1.5.4 stuff: builtin-checkout
Date: Mon, 17 Dec 2007 11:30:58 -0500 [thread overview]
Message-ID: <1197909058.8688.2.camel@hinata.boston.redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0712151529300.5349@iabervon.org>
On Sat, 2007-12-15 at 15:44 -0500, Daniel Barkalow wrote:
> I've got my builtin-checkout implementation at:
>
> git://iabervon.org/~barkalow/git.git builtin-checkout
>
> This may be interesting to some other people at this point, despite it not
> being relevant to 1.5.4, because (a) it includes a slew of small
> preliminary patches to other stuff that might be useful for making other
> things builtin and (b) these changes reflect my debugging of my naive
> implementation of builtin-checkout, and may suggest things that might be
> wrong in existing builtins that do multiple operations in the same
> process.
Thanks, fetching it now.
Kristian
prev parent reply other threads:[~2007-12-17 16:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-15 20:44 Post-1.5.4 stuff: builtin-checkout Daniel Barkalow
2007-12-17 16:30 ` Kristian Høgsberg [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=1197909058.8688.2.camel@hinata.boston.redhat.com \
--to=krh@redhat.com \
--cc=barkalow@iabervon.org \
--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).