Re: git subtree: an alternative to git submodule

[Ping Yin <pkufranky@gmail.com>]

On Sat, May 16, 2009 at 2:31 AM, Avery Pennarun <apenwarr@gmail.com> wrote:
> On Fri, May 15, 2009 at 2:11 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> Avery Pennarun <apenwarr@gmail.com> writes:
>>> ...  Obviously I would need to write a man page, but I've been
>>> hesitant to do that in case people have suggestions that need the
>>> whole UI to change.  Perhaps that's a chicken-and-egg problem, though,...
>>
>> If you fear that you might get into a situation that the UI _must_ change
>> because it does not fit people's needs or workflows, that is a sign that
>> the UI and the workflow it was designed to support may not have been well
>> thought out yet.  At least, you do not even _know_ if it is well thought
>> out or not.  It is understandable that people would say "sounds cool,
>> could potentially be good, but I'll wait and see if it is real" and leave.
>
> Well, I'm already using it myself in my own projects and I like it.
> So I'm pretty confident that it is *a* useful workflow.  Whether it's
> useful for others is a good question, and the only way to know the
> answer is to put it out there.
>
> But I'm at a bit of a loss as to why so many people (er, as compared
> to none) seem to have gotten excited about the tool, but then it
> fizzled.  This implies to me that something is missing.  Perhaps it's
> just the documentation; I'll work on that next, then.
>

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).

I don't whether this is a common reason, but at least it is the reason for me.