From: Kevin Wolf <kwolf@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] git rm Changelog?
Date: Tue, 25 Jan 2011 15:49:44 +0100 [thread overview]
Message-ID: <4D3EE308.3@redhat.com> (raw)
In-Reply-To: <4D3EDFCC.7020609@codemonkey.ws>
Am 25.01.2011 15:35, schrieb Anthony Liguori:
> On 01/25/2011 03:57 AM, Kevin Wolf wrote:
>> Am 25.01.2011 00:06, schrieb Paolo Bonzini:
>>
>>> ... or at least "git mv Changelog Changelog.old"?
>>>
>>> It only goes back to 0.12.0 so that there is hardly a place in the git
>>> repo to look for new features in 0.13 and 0.14.
>>>
>> Or maybe update it?
>>
>> I find it rather unfriendly to our users to say "Here is a new release.
>> In the unlikely case that you really want to know what has changed,
>> please bother yourself to filter the interesting stuff out of these
>> thousand git commits".
>>
>
> Logistically, I prefer doing highlights in a mail verses having a
> committed file. A Changelog file needs to be committed prior to tagging
> a release and cannot be enhanced after the fact. The nice bit about an
> email is that folks can respond to it with additional details.
>
> A wiki page (similar to what kernel newbies does) would be nice to
> supplement what's included in the release notes.
We do have a wiki page "ChangeLog" and there are more than enough links
to it, it just hasn't been updated since 0.12.5.
I don't really care too much in which way we do it. But for 0.13 we
don't have any kind of a high-level changelog on qemu.org or in the
release tarball, and I think we should.
Kevin
next prev parent reply other threads:[~2011-01-25 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 23:06 [Qemu-devel] git rm Changelog? Paolo Bonzini
2011-01-25 9:57 ` Kevin Wolf
2011-01-25 11:19 ` [Qemu-devel] " Paolo Bonzini
2011-01-25 14:35 ` [Qemu-devel] " Anthony Liguori
2011-01-25 14:49 ` Kevin Wolf [this message]
2011-01-25 15:00 ` Paolo Bonzini
2011-01-26 0:52 ` Miguel Di Ciurcio Filho
2011-01-26 2:05 ` Anthony Liguori
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=4D3EE308.3@redhat.com \
--to=kwolf@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=pbonzini@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).