All of lore.kernel.org
 help / color / mirror / Atom feed
From: Finn Arne Gangstad <finnag@pvv.org>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH/RFC 1/2] Add 'git subtree' command for tracking history of subtrees separately.
Date: Thu, 30 Apr 2009 10:58:53 +0200	[thread overview]
Message-ID: <20090430085853.GA21880@pvv.org> (raw)
In-Reply-To: <32541b130904291927m33908bacg2dbafcf64877b88f@mail.gmail.com>

On Wed, Apr 29, 2009 at 10:27:44PM -0400, Avery Pennarun wrote:
> Many projects are made of a combination of several subprojects/libraries and
> some application-specific code.  In some cases, particularly when the
> subprojects are all maintained independently, 'git submodule' is the best
> way to deal with this situation.  But if you frequently change the
> subprojects as part of developing your application, use multiple branches,
> and sometimes want to push your subproject changes upstream, the overhead of
> manually managing submodules can be excessive.
> 
> 'git subtree' provides an alternative mechanism, based around the
> 'git merge -s subtree' merge strategy.  Instead of tracking a submodule
> separately, you merge its history into your main project, and occasionally
> extract a new "virtual history" from your mainline that can be easily merged
> back into the upstream project.  The virtual history can be incrementally
> expanded as you make more changes to the superproject.

We have the exact same situation. I wanted to attack this from the
other end though, make submodules useable also in this scenario. The
subtree solution seems to be much easier to do in git, so maybe this
is a better approach!

Let's say you have three different projects that all use some shared
modules, The following operations should all be easy and fully
supported:

a) Modify project + some shared modules (in your project) with single commit
b) Push project + shared modules (for your project)
c) Push modifications to shared modules
d) Merge upstream version of shared modules into your project.

My quick analysis:
Your subtrees: a & b are easy, c & d are painful
Current submodules: a & b are painful, c & d are tolerable (somewhat tedious
with many shared modules, easy with one)

Subtrees also have the advantage that all the existing local tools
will be a lot more useful without any modifications (gitk, git gui,
git diff/patch/am/log/...)

To make subtrees realy useful, it would be good if you could improve c
& d, syncing with the shared modules!

- Finn Arne

  parent reply	other threads:[~2009-04-30  8:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-26 22:29 [PATCH/RFC 1/2] Add 'git subtree' command for tracking history of subtrees separately Avery Pennarun
2009-04-26 22:29 ` [PATCH/RFC 2/2] Automated test script for 'git subtree' Avery Pennarun
2009-04-30  2:27 ` [PATCH/RFC 1/2] Add 'git subtree' command for tracking history of subtrees separately Avery Pennarun
2009-04-30  3:44   ` Ping Yin
2009-04-30  8:58   ` Finn Arne Gangstad [this message]
2009-04-30 14:32     ` Avery Pennarun
2009-07-16 18:04       ` Andrey Smirnov
2009-07-16 18:34         ` Avery Pennarun
2009-07-16 22:09           ` Andrey Smirnov
2009-07-16 22:27             ` Avery Pennarun
2009-07-17  7:16               ` Andrey Smirnov
2009-07-17 15:47                 ` Avery Pennarun
2009-07-17 17:46                   ` Andrey Smirnov

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=20090430085853.GA21880@pvv.org \
    --to=finnag@pvv.org \
    --cc=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.