Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 24 Aug 2015 15:59:23 +0530	[thread overview]
Message-ID: <20150824102923.GA21306@dhcppc13.redhat.com> (raw)
In-Reply-To: <20150824091005.GA10044@dhcp-16-198.nay.redhat.com>

On 24/08/2015:05:10:05 PM, Dave Young wrote:
> kexec --version reports like below:
> kexec-tools 2.0.7 released 05 February 2015
> 
> The date string is generated when one run bootstrap script, thus
> it is more like a build date instead of release date.
> Even for distribution like Fedora it will make more sense if it can
> report something like "kexec-tools 2.0.7-1 released 05 February 2015"
> 
> In case building from git tree, the date cause more confusion.
> So let's remove it from version string unless there is better idea
> to resolve the issue.

May be we can take same approach what kernel build takes. Kernel build does not
add build/release string. It just add date and time like "Mon Aug 10 23:38:23 UTC 2015".

$ uname -a
Linux dhcppc13 4.1.5-200.fc22.x86_64 #1 SMP Mon Aug 10 23:38:23 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux

~Pratyush

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

  reply	other threads:[~2015-08-24 10:29 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 [this message]
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
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=20150824102923.GA21306@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