From: Jakub Narebski <jnareb@gmail.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: git@vger.kernel.org
Subject: Re: git-describe --contains fails on given tree
Date: Sat, 21 Aug 2010 12:55:53 -0700 (PDT) [thread overview]
Message-ID: <m3occvoi5c.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.LSU.2.01.1008212145520.14934@obet.zrqbmnf.qr>
Jan Engelhardt <jengelh@medozas.de> writes:
> Hi,
>
>
>
> for some reason, git-describe cannot figure out v1.17~15^2^2 in
> the pam_mount tree, despite me being able to actually give
> a description that would fit the contains syntax:
>
> $ git clone
> git://pam-mount.git.sf.net/gitroot/pam-mount/pam-mount
> Initialized empty Git repository in /dev/shm/pam-mount/.git/
> remote: Counting objects: 7261, done.
> remote: Compressing objects: 100% (1819/1819), done.
> remote: Total 7261 (delta 5557), reused 6990 (delta 5348)
> Receiving objects: 100% (7261/7261), 1.40 MiB | 832 KiB/s, done.
> Resolving deltas: 100% (5557/5557), done.
>
> $ cd pam-mount/
> $ git describe --contains v1.17~15^2^2
> fatal: cannot describe '95ce932690dfce8cbe50b6a3a8949e41a54c8966'
>
> (Expected to get back: v1.17~15^2^2)
>
> Why would it not want to return something? Possible bug?
Is v1.17 an *annotated* tag? What does
$ git describe --contains --tags v1.17~15^2^2
return?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-08-21 19:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 19:47 git-describe --contains fails on given tree Jan Engelhardt
2010-08-21 19:55 ` Jakub Narebski [this message]
2010-08-21 20:42 ` Jan Engelhardt
2010-08-22 21:58 ` Thomas Rast
2010-08-23 11:26 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3occvoi5c.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jengelh@medozas.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).