Re: Re: [RFC v2] submodule: Respect requested branch on all clones

From: Francesco Pretto <ceztko@gmail.com>
Date: Jan 6, 2014, 23:32 UTC
Message-ID: <CALas-ijNgaTQr77DZw3acypgaJHpDFVnGdq97ECM4zu+CPma0w@mail.gmail.com>
In-Reply-To: <CALas-ijXQFcUHWk-jJrLifqsMHAKo6NNKya+jR6RJGGDXY76hg@mail.gmail.com>

2014/1/7 Francesco Pretto <ceztko@gmail.com>:

Show 7 quoted lines

> To not break the existing behavior what it's really needed here, IMO,
> is a "submodule.<name>.attached" property that says two things:
> - at the first clone on "git submodule update" stay attached to
> "submodule.<name>.branch";
> - implies "--remote", as it's the only thing that makes sense when the
> submodules are attached.
>

Unless you decide to go with the proposed approach of Trevor, where "submodule.<name>.branch" set means attached (if it's not changed: this thread is quite hard to follow...). To this end, Junio could sync with more "long-timers" (Heiko?) submodule users/devs to understand if this breaks too much or not.