public inbox for kexec@lists.infradead.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: Dave Young <dyoung@redhat.com>
Cc: kexec@lists.infradead.org, Baoquan <bhe@redhat.com>
Subject: Re: [ANNOUNCE] kexec-tools 2.0.4
Date: Thu, 28 Mar 2013 11:45:03 +0900	[thread overview]
Message-ID: <20130328024458.GA7171@verge.net.au> (raw)
In-Reply-To: <5153A107.1040705@redhat.com>

On Thu, Mar 28, 2013 at 09:46:47AM +0800, Dave Young wrote:
> On 03/27/2013 08:34 PM, Simon Horman wrote:
> > On Thu, Mar 21, 2013 at 06:00:29PM +0800, Dave Young wrote:
> >> On 03/21/2013 05:02 PM, Baoquan wrote:
> >>> On 03/21/2013 04:56 PM, Baoquan wrote:
> >>>
> >>>> On 03/21/2013 04:51 PM, Simon Horman wrote:
> >>>>
> >>>>> On Thu, Mar 21, 2013 at 03:14:11PM +0800, Baoquan wrote:
> >>>>>> Hi Simon,
> >>>>>>
> >>>>>> After "git pull", I didn't find release 2.0.4. Could you please double
> >>>>>> check it?
> >>>>>
> >>>>> Please try v2.0.4, it is a tag in git.
> >>>>
> >>>>
> >>>
> >>>
> >>> Hi,
> >>>
> >>> Sorry, I just create a new dir and "git clone", v2.0.4 can be seen now.
> >>> But in my old clone, "git pull" can't get v2.0.4. It's a little weird.
> >>
> >> Looks like the commit is not in master branch, the tag v2.0.4 itself is ok.
> >>
> >> git log --oneline
> >>
> >> b2dc426 s390: Replace clgfi with cghi
> >> 56af4f5 kexec: use _ALIGN* to make the logic clear
> >> 337d4fc kexec: ppc64: use _ALIGN* to make the logic clear
> >> bb3f9f5 kexec: ppc: use _ALIGN* to make the logic clear
> >> f36d320 kexec: x86_64: use _ALIGN* to make the logic clear
> >> 58a22bd kexec: sh: use _ALIGN* to make the logic clear
> >> 333f487 kexec: s390: remove ALIGN_UP and use _ALIGN_UP
> >> d41a4db kexec: mips: use _ALIGN* to make the logic clear
> >> e8a7f63 kexec: ia64: use _ALIGN* to make the logic clear
> >> cf190f6 kexec: arm: use _ALIGN* to make the logic clear
> >> 8388bdc kexec: i386: use _ALIGN* to make the logic clear
> >> 0c1b89d kexec: ppc: remove duplicated _ALIGN_* macros
> >> 412561a kexec: use _ALIGN() instead of align()
> >> 9ea6e05 kexec: add _ALIGN* marcos for align operation
> >> 5db7ba5 kexec: check size before trying the malloc
> >> ...
> > 
> > Strange. I have pushed again.
> > 
> 
> It's ok now, thanks!
> 
> git log --oneline
> ...
> 3a33a60 kexec: fix possible memory leak in check_reuse_initrd
> fa101c3 kexec: Fix Makefile of linking kdump file
> 8f1cfc6 kexec-tools 2.0.4.git
> 709dee5 kexec-tools 2.0.4
> b2dc426 s390: Replace clgfi with cghi
> ...

Great, thanks for checking.

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

      reply	other threads:[~2013-03-28  2:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19  2:11 [ANNOUNCE] kexec-tools 2.0.4 Simon Horman
2013-03-21  7:14 ` Baoquan
2013-03-21  8:51   ` Simon Horman
2013-03-21  8:56     ` Baoquan
2013-03-21  9:02       ` Baoquan
2013-03-21 10:00         ` Dave Young
2013-03-27 12:34           ` Simon Horman
2013-03-28  1:46             ` Dave Young
2013-03-28  2:45               ` 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=20130328024458.GA7171@verge.net.au \
    --to=horms@verge.net.au \
    --cc=bhe@redhat.com \
    --cc=dyoung@redhat.com \
    --cc=kexec@lists.infradead.org \
    /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