From: Ping Yin <pkufranky@gmail.com>
To: Avery Pennarun <apenwarr@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: Tue, 19 May 2009 22:27:03 +0800 [thread overview]
Message-ID: <46dff0320905190727m77a582c1j5ddc161230cc4a83@mail.gmail.com> (raw)
In-Reply-To: <32541b130905180938v5dd5283g6b75ffb7e76f3280@mail.gmail.com>
On Tue, May 19, 2009 at 12:38 AM, Avery Pennarun <apenwarr@gmail.com> wrote:
> 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.
>
Some problems after trying.
* "split" generates a commit hash which i take some time to figure out
the meaning. May it should accept one more argument (repository name)
to generate the repository directly?
* "pull" creates the merged files to the wrong directory. Following is
the output
git subtree -d pull --prefix=foo git@example.com:foo.git master
command: {pull}
quiet: {}
revs: {}
dir: {foo}
opts: {git@example.com:foo.git master}
+ git pull -s subtree git@example.com:foo.git master
From example.com:foo
* branch master -> FETCH_HEAD
Merge made by subtree.
scripts/data.example/creatives/1.swf | Bin 0 -> 174109 bytes
scripts/data.example/creatives/2.swf | Bin 0 -> 103622 bytes
scripts/data.example/creatives/3.swf | Bin 0 -> 35347 bytes
scripts/data.example/creatives/4.swf | Bin 0 -> 16300 bytes
5 files changed, 0 insertions(+), 0 deletions(-)
...
* "merge" doesn't respect the prefix option. With the following
commands, foo.txt is not merged to subdir foo/
touch foo.txt && git add foo.txt && git commit -m "add foo.txt"
git branch foo && git reset --hard HEAD^
git subtree merge --prefix=foo foo
next prev parent reply other threads:[~2009-05-19 14:27 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
2009-05-19 14:27 ` Ping Yin [this message]
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=46dff0320905190727m77a582c1j5ddc161230cc4a83@mail.gmail.com \
--to=pkufranky@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@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).