Re: Finding a tag that introduced a submodule change

On Wed, Mar 15, 2017 at 10:10 AM, Stefan Beller wrote: > On Fri, Mar 3, 2017 at 7:40 AM, Robert Dailey > wrote: >> I have a repository with a single submodule in it. Since the parent >> repository represents the code base for an actual product, I

Re: Finding a tag that introduced a submodule change

On Fri, Mar 3, 2017 at 7:40 AM, Robert Dailey wrote: > I have a repository with a single submodule in it. Since the parent > repository represents the code base for an actual product, I tag > release versions in the parent repository. I do not put tags in the > submodule

Re: Finding a tag that introduced a submodule change

On Fri, Mar 3, 2017 at 12:04 PM, Junio C Hamano wrote: > Robert Dailey writes: > >> Sometimes I run into a situation where I need to find out which >> release of the product a submodule change was introduced in. This is >> nontrivial, since there are

Re: Finding a tag that introduced a submodule change

Robert Dailey writes: > Sometimes I run into a situation where I need to find out which > release of the product a submodule change was introduced in. This is > nontrivial, since there are no tags in the submodule itself. Does your superproject rewind the commit in the

Re: Finding a tag that introduced a submodule change

On Fri, Mar 3, 2017 at 7:40 AM, Robert Dailey wrote: > I have a repository with a single submodule in it. Since the parent > repository represents the code base for an actual product, I tag > release versions in the parent repository. I do not put tags in the > submodule

Finding a tag that introduced a submodule change

I have a repository with a single submodule in it. Since the parent repository represents the code base for an actual product, I tag release versions in the parent repository. I do not put tags in the submodule since multiple other products may be using it there and I wanted to avoid ambiguous