From: Pratyush Anand <panand@redhat.com>
To: Dave Young <dyoung@redhat.com>
Cc: Simon Horman <horms@verge.net.au>, kexec@lists.infradead.org
Subject: Re: [PATCH RFC] Drop release date from kexec-tools version output
Date: Thu, 27 Aug 2015 13:19:30 +0530 [thread overview]
Message-ID: <20150827074930.GJ13340@dhcppc13.redhat.com> (raw)
In-Reply-To: <20150827062956.GD3427@dhcp-129-155.nay.redhat.com>
On 27/08/2015:02:29:57 PM, Dave Young wrote:
> Pratyush, rethink about it, it is still confused. Considering below case:
>
> git clone kexec-tools;
> bootstrap and build, the version and date is the current git version and current date
> after some time, git pull, upstream bumps to new version
> run make again, build/sbin/kexec --version will still show the old date along with new version
OK, got it..
May be we can take this patch and then it will be good to take Geoff's following patch.
http://git.kernel.org/cgit/linux/kernel/git/geoff/kexec-tools.git/commit/?id=0b18e1d9311e21d2a2f1392607eade138b9aefe7
With this patch we get something like this:
$ ./build/sbin/kexec -v
kexec version: 15.05.14.11.29-g4f6d8ec17529
kexec-tools 2.0.10.git released 27 August 2015
So, we have Date, Time and git shaid as well.
~Pratyush
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2015-08-27 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-24 9:10 [PATCH RFC] Drop release date from kexec-tools version output Dave Young
2015-08-24 10:29 ` Pratyush Anand
2015-08-25 8:47 ` Dave Young
2015-08-25 10:42 ` Pratyush Anand
2015-08-27 6:29 ` Dave Young
2015-08-27 7:49 ` Pratyush Anand [this message]
2015-09-02 1:00 ` Simon Horman
2015-09-02 1:25 ` Dave Young
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=20150827074930.GJ13340@dhcppc13.redhat.com \
--to=panand@redhat.com \
--cc=dyoung@redhat.com \
--cc=horms@verge.net.au \
--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