From: Leif Gruenwoldt <leifer@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH] add update to branch support for "floating submodules"
Date: Sat, 10 Dec 2011 10:27:28 -0500 [thread overview]
Message-ID: <CALFF=ZQKRgx_AodBQH17T9cSe_JFtoKie7DoMMfkTXCyCFospw@mail.gmail.com> (raw)
In-Reply-To: <7vborhaqgw.fsf@alter.siamese.dyndns.org>
On Sat, Dec 10, 2011 at 1:30 AM, Junio C Hamano <gitster@pobox.com> wrote:
> So that use case does not sound like a good rationale to require addition
> of floating submodules.
Ok I will try another scenario :)
Imagine again products A, B and C and a common library. The products are in
a stable state of development and track a stable branch of the common lib.
Then imagine an important security fix gets made to the common library. On
the next pull of products A, B, and C they get this fix for free
because they were
floating. They didn't need to communicate with the maintainer of the common
repo to know this. In fact they don't really care. They just want the
latest stable
code for that release branch.
This is how package management on many linux systems works. Dependencies
get updated and all products reap the benefit (or catastrophe) automatically.
next prev parent reply other threads:[~2011-12-10 15:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-09 17:40 [RFC/PATCH] add update to branch support for "floating submodules" Heiko Voigt
2011-11-09 18:01 ` Junio C Hamano
2011-11-29 22:08 ` Heiko Voigt
2011-12-10 5:50 ` Leif Gruenwoldt
2011-12-10 6:19 ` Jonathan Nieder
2011-12-10 6:30 ` Junio C Hamano
2011-12-10 15:27 ` Leif Gruenwoldt [this message]
2011-12-12 15:34 ` Andreas T.Auer
2011-12-12 18:04 ` Leif Gruenwoldt
2011-12-12 18:42 ` Andreas T.Auer
2011-12-12 19:13 ` Leif Gruenwoldt
2011-12-12 22:31 ` Jens Lehmann
2011-12-12 22:56 ` Phil Hord
2011-12-13 15:35 ` Marc Branchaud
2011-12-13 21:19 ` Jens Lehmann
2011-12-13 22:42 ` Marc Branchaud
2011-12-12 19:36 ` Junio C Hamano
2011-12-13 14:17 ` Phil Hord
2011-12-13 21:09 ` Jens Lehmann
2012-01-30 21:15 ` Phil Hord
2012-01-31 20:55 ` Jens Lehmann
2012-01-31 22:50 ` Phil Hord
2012-02-01 22:37 ` Jens Lehmann
2012-02-06 17:31 ` Phil Hord
2012-02-06 21:32 ` Jens Lehmann
2011-12-13 0:12 ` Brandon Casey
2011-12-10 14:16 ` Gioele Barabucci
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='CALFF=ZQKRgx_AodBQH17T9cSe_JFtoKie7DoMMfkTXCyCFospw@mail.gmail.com' \
--to=leifer@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).