I think I've run in to a bug in 'git describe' (reproduced with git
2.11.0, 2.16.1, and 2.19.0.221.g150f307af).
I've got two tiny git repos whose commit graphs are identical, but where
'git describe' gives different results.
* merge 1.1
Sebastian Kuzminsky writes:
> I've got two tiny git repos whose commit graphs are identical, but
> where 'git describe' gives different results.
> ...
> The histories differ only in the timestamps of the commits...
describe does take the commit timestamps into account, so it is
expected you woul
On 9/24/18 4:24 PM, Junio C Hamano wrote:
Sebastian Kuzminsky writes:
I've got two tiny git repos whose commit graphs are identical, but
where 'git describe' gives different results. ... The histories
differ only in the timestamps of the commits...
describe does take the commit timestamps i
On Tue, Sep 25, 2018 at 5:41 PM Sebastian Kuzminsky wrote:
> That behavior seems to me to be different from what the (2.11) manpage says:
Good opportunity to improve the man page anyway even if Junio is
right. I agree that the section about "search strategy" is a bit
misleading because it does no
On Tue, Sep 25, 2018 at 6:05 PM Duy Nguyen wrote:
>
> On Tue, Sep 25, 2018 at 5:41 PM Sebastian Kuzminsky wrote:
> > That behavior seems to me to be different from what the (2.11) manpage says:
>
> Good opportunity to improve the man page anyway even if Junio is
> right. I agree that the section
On Fri, Sep 27, 2019 at 02:02:01PM +0200, SZEDER Gábor wrote:
> On Fri, Sep 27, 2019 at 11:51:07AM +0200, Anders Janmyr wrote:
> > I'm not sure if this is a bug or not but `git describe` gives
> > different results when the repo has been cloned with `--depth` or not.
> >
> > In the example below f
Hi,
I'm not sure if this is a bug or not but `git describe` gives
different results when the repo has been cloned with `--depth` or not.
In the example below from the git repository the number of additional
commits since the
last tag differs 256 vs. 265.
```
$ git clone https://github.com/git/gi
I didn't get back the latest tag by 'git describe --tags --always' if
I have two tags on the same commit.
// repository ppa:git-core/ppa
(master)⚡ % cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.2 LTS"
(master)⚡ % git --ver
On Fri, Sep 27, 2019 at 11:51:07AM +0200, Anders Janmyr wrote:
> Hi,
>
> I'm not sure if this is a bug or not but `git describe` gives
> different results when the repo has been cloned with `--depth` or not.
>
> In the example below from the git repository the number of additional
> commits since
On Sun, Feb 12, 2017 at 01:15:22PM +0100, Istvan Pato wrote:
> I didn't get back the latest tag by 'git describe --tags --always' if
> I have two tags on the same commit.
>
> // repository ppa:git-core/ppa
>
> (master)⚡ % cat /etc/lsb-release
> DISTRIB_ID=Ubuntu
> DISTRIB_RELEASE=16.04
> DISTRIB_
Kevin Daudt writes:
> On Sun, Feb 12, 2017 at 01:15:22PM +0100, Istvan Pato wrote:
>
>> (master) [1] % git show-ref --tag
>> 76c634390... refs/tags/1.0.0
>> b77c7cd17... refs/tags/1.1.0
>> b77c7cd17... refs/tags/1.2.0
>>
>> (master) % git describe --tags --always
>> 1.1.0-1-ge9e9ced
>>
>> ### E
This is my fault: this is a lightweight tag.
Thank you!
2017-02-13 21:35 GMT+01:00 Junio C Hamano :
> Kevin Daudt writes:
>
>> On Sun, Feb 12, 2017 at 01:15:22PM +0100, Istvan Pato wrote:
>>
>>> (master) [1] % git show-ref --tag
>>> 76c634390... refs/tags/1.0.0
>>> b77c7cd17... refs/tags/1.1.0
>>
12 matches
Mail list logo
