From: George Dunlap <george.dunlap@eu.citrix.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Ian Jackson <ian.jackson@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
Ian Campbell <ian.campbell@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH for-xen-4.5] tools/mkrpm: improve version.release handling
Date: Mon, 3 Nov 2014 14:32:22 +0000 [thread overview]
Message-ID: <545791F6.2080809@eu.citrix.com> (raw)
In-Reply-To: <20141103142436.GA23458@aepfle.de>
On 11/03/2014 02:24 PM, Olaf Hering wrote:
> On Mon, Nov 03, George Dunlap wrote:
>
>> How difficult would it be to have this be something sensible like,
>> "changesets since last tag"?
> Very difficult, because one does changes without commit, runs 'make
> rpmball' and expects that rpm -Fvh *.rpm continues to work.
Right. Personally, I think trying to make "rpm -Fvh" work for all the
use cases a developer might want is more hassle than it's worth; as I
said, I have scripts that just do "rpm -e" in such cases. I wouldn't
oppose it, but I don't really support it either.
Ian / Ian / Wei, any thoughts?
-George
next prev parent reply other threads:[~2014-11-03 14:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 15:01 [PATCH for-xen-4.5] tools/mkrpm: improve version.release handling Olaf Hering
2014-10-07 15:03 ` Olaf Hering
2014-10-29 8:17 ` Olaf Hering
2014-11-03 11:00 ` George Dunlap
2014-11-03 14:16 ` George Dunlap
2014-11-03 14:19 ` George Dunlap
2014-11-03 14:24 ` Olaf Hering
2014-11-03 14:29 ` Ian Campbell
2014-11-03 14:47 ` Olaf Hering
2014-11-04 10:11 ` Ian Campbell
2014-11-04 10:16 ` Olaf Hering
2014-11-03 14:32 ` George Dunlap [this message]
2014-11-03 14:48 ` Olaf Hering
2014-11-04 10:37 ` George Dunlap
2014-11-04 10:46 ` Olaf Hering
2014-11-04 11:00 ` George Dunlap
2014-11-04 11:03 ` Ian Campbell
2014-11-07 13:30 ` Olaf Hering
2014-11-07 14:52 ` Konrad Rzeszutek Wilk
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=545791F6.2080809@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=olaf@aepfle.de \
--cc=stefano.stabellini@eu.citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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 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.