On Thu, Jul 22, 2010 at 5:33 PM, Avery Pennarun <apenwarr@xxxxxxxxx> wrote:
> On Thu, Jul 22, 2010 at 4:17 PM, Ęvar Arnfjörš Bjarmason
> <avarab@xxxxxxxxx> wrote:
>> But it's also clear that we have a lot of tribal knowledge about the
>> lackings of git submodule / git subtree. It would be *really* useful
>> if people like Avery and Jens which have obviously thought hard about
>> the submodule/subtree issues would draft up some (calmly written) docs
>> about how the two differ (with comparison tables etc.).
>>
>> That'd be a very helpful resource for Git users in deciding which one
>> to use.
>
> I think I'm too biased to write that, but if someone else wants to
> take the lead, I could certainly contribute.
>
> Have fun,
>
> Avery
I personally tried to understand submodules, but my attempts to find
easy way to use them have failed miserably;) probably i have to spend
even more time in order to understand if i can benefit from them or
not. So, i think this kind of comparison would be very beneficial for
"mere mortals"
I would like to share an idea how it can be organized:
We could create a file in doc section of git.git or in Avery's repo
named git_submodule_vs_git_subtree or just use a separate topic of the
list.
The file would look like this:
git-submodule | feature | git-subtree
______________________________________________________________________
+ | ability to tag submodule without | -
(comments) | tagging the whole tree | (comments)
______________________________________________________________________
Avery and Jens could add features they think are beneficial for one
project or another and answer to each other this way. They could mark
just presence or abscence of the feature by +/- like above or specify
key approaches how to do different things.
For example, how to configure new submodule (main sequence of commands
to create, add ), how to do that with sub-tree...
I think this simple feature matrix will answer a lot of questions.
just my 2 cents...
Thanks,
Eugene
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html