From: Simon Horman <horms@verge.net.au>
To: Don Zickus <dzickus@redhat.com>
Cc: "Américo Wang" <xiyou.wangcong@gmail.com>, kexec@lists.infradead.org
Subject: Re: kexec-tools git tree is tagged incorrectly?
Date: Fri, 18 Nov 2011 08:19:10 +0900 [thread overview]
Message-ID: <20111117231909.GF10187@verge.net.au> (raw)
In-Reply-To: <20111116155103.GG8685@redhat.com>
On Wed, Nov 16, 2011 at 10:51:03AM -0500, Don Zickus wrote:
> On Wed, Nov 16, 2011 at 11:35:03AM +0900, Simon Horman wrote:
> > On Wed, Nov 16, 2011 at 10:04:06AM +0800, Américo Wang wrote:
> > > On Wed, Nov 16, 2011 at 9:12 AM, Simon Horman <horms@verge.net.au> wrote:
> > > >
> > > > Hi Américo,
> > > >
> > > > I'm not sure that I understand your question, but
> > > > 920f4ededd9627add3ca1cdea965d204f2ca43a7 is the HEAD of the master
> > > > (development) branch. And unless I am mistaken, it is a descendent of v2.0.2.
> > > >
> > >
> > > Yeah, so `git describe HEAD` should show v2.0.2-BLAHBLAH, not
> > > v1.101-618-g920f4ed, right?
> >
> > Yes, I think so. I'm rather unsure why it isn't.
> > However, the following does seem to give a result more in line with
> > expectations.
>
> Are you creating annotated tags or lightweight tags? That might be the
> difference.
I believe I am creating lightweight tags,
I guess that is the cause of the difference.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2011-11-17 23:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 12:51 kexec-tools git tree is tagged incorrectly? Américo Wang
2011-11-16 1:12 ` Simon Horman
2011-11-16 2:04 ` Américo Wang
2011-11-16 2:35 ` Simon Horman
2011-11-16 15:26 ` Américo Wang
2011-11-16 15:51 ` Don Zickus
2011-11-17 23:19 ` Simon Horman [this message]
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=20111117231909.GF10187@verge.net.au \
--to=horms@verge.net.au \
--cc=dzickus@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=xiyou.wangcong@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.