From: Thomas Koch <thomas@koch.ro>
To: Tim Visher <tim.visher@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [Feature Request] git export
Date: Mon, 10 Aug 2009 18:41:00 +0200 [thread overview]
Message-ID: <200908101841.00522.thomas@koch.ro> (raw)
In-Reply-To: <c115fd3c0908100927v4d9e4a87we4502e91d3789138@mail.gmail.com>
Hi Tim,
thanks for your explanation. Still I don't get how to do it with git checkout-
index. The man page says "Just read the desired tree into the index", but I
don't know what is meant by this.
> Hey Thomas,
>
> On Mon, Aug 10, 2009 at 12:22 PM, Thomas Koch<thomas@koch.ro> wrote:
> > could you please provide a simple solution to save a tree object into an
> > arbitrary location?
>
> This has been requested a few times and I have no idea what the
> development status of it is. Most people seem to recommend just
> making an alias around git checkout-index.
>
> > I found some hints, that it would be possible by missusing either git
> > checkout-index or git-archive, but I think that it shouldn't require that
> > much GIT FU to do such a simple thing.
>
> It's not really a misuse, as the [man page
> itself](http://www.kernel.org/pub/software/scm/git/docs/git-checkout-index.
>html) recommends using checkout-index as a way to export an entire tree.
> Until someone decides that it's worth making the porcelain command (like
> you perhaps) then I think you can just stick with checkout-index knowing
> you're not abusing anything.
Thomas Koch, http://www.koch.ro
next prev parent reply other threads:[~2009-08-10 16:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-10 16:22 [Feature Request] git export Thomas Koch
2009-08-10 16:27 ` Tim Visher
2009-08-10 16:41 ` Thomas Koch [this message]
2009-08-10 18:31 ` Tim Visher
2009-08-10 16:54 ` Junio C Hamano
2009-08-10 16:56 ` Johannes Schindelin
2009-08-11 7:50 ` Michael J Gruber
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=200908101841.00522.thomas@koch.ro \
--to=thomas@koch.ro \
--cc=git@vger.kernel.org \
--cc=tim.visher@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.