Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: "Américo Wang" <xiyou.wangcong@gmail.com>
Cc: kexec@lists.infradead.org
Subject: Re: kexec-tools git tree is tagged incorrectly?
Date: Wed, 16 Nov 2011 10:12:21 +0900	[thread overview]
Message-ID: <20111116011221.GA6216@verge.net.au> (raw)
In-Reply-To: <CAM_iQpW8J7hybZVVLK9rtoMrWbU4AS82ob0iNdbAMCxv8hpC-A@mail.gmail.com>

On Tue, Nov 15, 2011 at 08:51:15PM +0800, Américo Wang wrote:
> Hello, Simon,
> 
> I am wondering why I get:
> 
> % git log --pretty=oneline -n 1
> 920f4ededd9627add3ca1cdea965d204f2ca43a7 kexec-tools: powerpc: Add
> more 64bit relocations
> 
> % git describe
> v1.101-618-g920f4ed
> 
> % git tag -l
> v1.101
> v2.0.0
> v2.0.0-rc1
> v2.0.1
> v2.0.1-rc1
> v2.0.2
> v2.0.2-rc1
> v2.0.2-rc2
> v20061214
> v20070319-rc
> v20070330
> v20071017-rc
> v20071030
> v20080219-rc
> v20080221-rc
> v20080226-rc
> v20080227
> v20080318-rc
> v20080324
> 
> HEAD should be v2.0.2, isn't it?

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.


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2011-11-16  1:12 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 [this message]
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

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=20111116011221.GA6216@verge.net.au \
    --to=horms@verge.net.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox