Re: Making submodules easier to work with (auto-update on checkout or merge, stash & restore submodules)

From: Ping Yin <pkufranky@gmail.com>
Date: Apr 30, 2008, 17:21 UTC
Message-ID: <46dff0320804301021t59740377vece412ea71d67cf4@mail.gmail.com>
In-Reply-To: <32541b130804300947s6083156etc6514cc13c24af13@mail.gmail.com>

On Thu, May 1, 2008 at 12:47 AM, Avery Pennarun <apenwarr@gmail.com> wrote:

> On 4/30/08, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
>  >  On Tue, 29 Apr 2008, Tim Harper wrote:

Show 5 quoted lines

>
>  Not true.  If ".gitmodules" is different between branches, then
>  .git/config will have the wrong information.  I think this was the
>  reason for the "read .gitmodules directly and don't worry about
>  .git/config" discussion/patches earlier.

I tried hard to avoid 'git submodule init' in that series. Unfortuately, few people agreed with me.

Show 8 quoted lines

>  We had some discussion on the list earlier about having submodule
>  checkouts automatically acquire a branch name, so that commits don't
>  get lost as easily.  I was going to think about this more and
>  eventually submit a patch, but I haven't gotten to it yet.  Anyway,
>  the idea is that you have a branch by default, so that you don't end
>  up in the useless situation of not being on a branch, which encourages
>  checking in without being on a branch, in the first place.
>

I like this idea and it is very useful for me.

-- 
Ping Yin