From: Fam Zheng <famz@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: Eric Blake <eblake@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] configure: save git working tree information in "pkgversion"
Date: Wed, 1 Jun 2016 17:11:02 +0800 [thread overview]
Message-ID: <20160601091102.GH8639@ad.usersys.redhat.com> (raw)
In-Reply-To: <fdd92597-e214-0dd7-7cc0-85aeab7010e5@redhat.com>
On Wed, 06/01 10:55, Laszlo Ersek wrote:
> (Anyway, this is moot now; I'll happily leave it to Fam! :))
Thanks, I wrote the code before you sent this, so I posted it today anyway. :)
Also note that we shouldn't do this at configure time, because between
./configure and make, the tree can be modified. That's why my patch is in
Makefile, and always checks the "dirtiness".
Fam
next prev parent reply other threads:[~2016-06-01 9:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 15:04 [Qemu-devel] [PATCH] configure: save git working tree information in "pkgversion" Laszlo Ersek
2016-05-31 15:14 ` Daniel P. Berrange
2016-05-31 15:40 ` Laszlo Ersek
2016-05-31 15:43 ` Daniel P. Berrange
2016-05-31 17:01 ` Laszlo Ersek
2016-05-31 17:45 ` Eric Blake
2016-05-31 21:16 ` Laszlo Ersek
2016-06-01 8:55 ` Laszlo Ersek
2016-06-01 9:11 ` Fam Zheng [this message]
2016-06-01 9:36 ` Kashyap Chamarthy
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=20160601091102.GH8639@ad.usersys.redhat.com \
--to=famz@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.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.