From: Avery Pennarun <apenwarr@gmail.com>
To: Ping Yin <pkufranky@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: git subtree: an alternative to git submodule
Date: Mon, 18 May 2009 12:38:56 -0400 [thread overview]
Message-ID: <32541b130905180938v5dd5283g6b75ffb7e76f3280@mail.gmail.com> (raw)
In-Reply-To: <46dff0320905180855m3e1bd74esb564af0fbcf4b1ff@mail.gmail.com>
On Mon, May 18, 2009 at 11:55 AM, Ping Yin <pkufranky@gmail.com> wrote:
> It's really a cool feature, but i havn't tried it. Why?
>
> It will spends me some time saving and applying the patches and then
> testing it (i don't have the appropriate environment setuped). But I
> am busy and there is no urgent need to use this feature ( it is only a
> rare case for me). So i will wait until i need the feature or there
> is an easy to fetch the code ( pu of official reposotory or other
> repository with these patches applied).
Excellent, thanks for the feedback. In fact you can git clone the
code from here:
git clone git://github.com/apenwarr/git-subtree.git
(It's not a copy of the git repo; it's a tiny standalone repo.)
The important file is 'git-subtree'. Copy this anywhere on your PATH,
and magically the 'git subtree' command will work.
I admit that your next roadblock will probably be lack of
documentation, though, as Junio points out.
Have fun,
Avery
next prev parent reply other threads:[~2009-05-18 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 22:39 [PATCH/RFC RESEND 0/2] git subtree: an alternative to git submodule Avery Pennarun
2009-05-08 22:39 ` [PATCH/RFC RESEND 1/2] Add 'git subtree' command for tracking history of subtrees separately Avery Pennarun
2009-05-08 22:39 ` [PATCH/RFC RESEND 2/2] Automated test script for 'git subtree' Avery Pennarun
2009-05-15 16:09 ` git subtree: an alternative to git submodule Avery Pennarun
2009-05-15 18:11 ` Junio C Hamano
2009-05-15 18:31 ` Avery Pennarun
2009-05-18 15:55 ` Ping Yin
2009-05-18 15:55 ` Ping Yin
2009-05-18 16:38 ` Avery Pennarun [this message]
2009-05-19 14:27 ` Ping Yin
2009-05-19 16:13 ` Jakub Narebski
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=32541b130905180938v5dd5283g6b75ffb7e76f3280@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pkufranky@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).