Re: [PATCH/RFC 1/2] Add 'git subtree' command for tracking history of subtrees separately.

[Andrey Smirnov <allter@gmail.com>]

On Fri, Jul 17, 2009 at 7:47 PM, Avery Pennarun<apenwarr@gmail.com> wrote:
> The problem is that test-split and test-split-old are completely
> unrelated trees that have similar-looking files but no common
> ancestry.

I understand this but if two projects share the same commit history
for their subdir-lib
both test-split and test-split-old will have same root.

> git-rebase tries to be cleverer, and starts comparing patches and file
> similarities so it can graft one tree onto another,

That is too clear for me and since I try to avoid committing
'reversion commits' it works for my
workflow. I don't want to track library as separate ref (at least now).

Anyway thank you for great extension - will now try using it on a
regular basis - there're another project that is more suitable
to track libraries as you suggest.

--
Sincerly yours, Andrey.