On Wed, Oct 05, 2016 at 09:13:53AM -0700, Junio C Hamano wrote:
> Heiko Voigt writes:
>
> >> It IS a hack, but having this information in .git would
> >> mean that it can be forced to be in machine readable form, unlike a
> >> mention in README. I do not know if the .gitmodules/.gitignore
> >> c
Heiko Voigt writes:
>> It IS a hack, but having this information in .git would
>> mean that it can be forced to be in machine readable form, unlike a
>> mention in README. I do not know if the .gitmodules/.gitignore
>> combination is a sensible thing to use, but it does smell like a
>> potential
On Tue, Oct 04, 2016 at 12:01:13PM -0700, Junio C Hamano wrote:
> Junio C Hamano writes:
>
> > Stefan Beller writes:
> >
> >> I wonder if we could make that convenient for users by not tracking
> >> the submodule,
> >> i.e.
> >> * we have the information in the .gitmodules file
> >> * the path i
Junio C Hamano writes:
> Stefan Beller writes:
>
>> I wonder if we could make that convenient for users by not tracking
>> the submodule,
>> i.e.
>> * we have the information in the .gitmodules file
>> * the path itself is in the .gitignore
>> * no tree entry
>>
>> Then you can update to the rem
Stefan Beller writes:
>>
>> We already have options to support these kinds of workflows. Look at the
>> option '--remote' for 'git submodule update'.
>>
>> You then only have to commit the submodule if you do not want to see it
>> as dirty locally, but you will always get the tip of a remote trac
>
> We already have options to support these kinds of workflows. Look at the
> option '--remote' for 'git submodule update'.
>
> You then only have to commit the submodule if you do not want to see it
> as dirty locally, but you will always get the tip of a remote tracking
> branch when updating.
On Mon, Oct 03, 2016 at 12:00:45PM -0700, Junio C Hamano wrote:
> Jeremy Morton writes:
>
> > At the moment, supermodules must reference a given commit in each of
> > its submodules. If one is in control of a submodule and it changes on
> > a regular basis, this can cause a lot of overhead with
Jeremy Morton writes:
> At the moment, supermodules must reference a given commit in each of
> its submodules. If one is in control of a submodule and it changes on
> a regular basis, this can cause a lot of overhead with "submodule
> updated" commits in the supermodule. It would be useful of g
At the moment, supermodules must reference a given commit in each of
its submodules. If one is in control of a submodule and it changes on
a regular basis, this can cause a lot of overhead with "submodule
updated" commits in the supermodule. It would be useful of git allows
the option of refe
9 matches
Mail list logo
