From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Weil <sw@weilnetz.de>,
QEMU Developer <qemu-devel@nongnu.org>,
Pranith Kumar <bobby.prani@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Fix regressions caused by renaming README
Date: Wed, 20 Jul 2016 09:47:13 +0100 [thread overview]
Message-ID: <20160720084713.GE29602@redhat.com> (raw)
In-Reply-To: <CAFEAcA-gy2pxvcng78kVqmUoYwdWhU2gtidMgdyMMbNvt_RVxw@mail.gmail.com>
On Tue, Jul 19, 2016 at 09:53:30PM +0100, Peter Maydell wrote:
> On 19 July 2016 at 18:47, Stefan Weil <sw@weilnetz.de> wrote:
> > Commit e5dfc5e8e715c572aea44ac4d96c43941d4741c7 renamed README but did not
> > update scripts/checkpatch.pl. Fix this.
> >
> > An update was also needed for qemu.nsi (Windows).
> >
> > Reported-by: Daniel P. Berrange <berrange@redhat.com>
> > Signed-off-by: Stefan Weil <sw@weilnetz.de>
> > ---
> > qemu.nsi | 4 ++--
> > scripts/checkpatch.pl | 2 +-
> > 2 files changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/qemu.nsi b/qemu.nsi
> > index a20f6ef..c037017 100644
> > --- a/qemu.nsi
> > +++ b/qemu.nsi
> > @@ -116,7 +116,7 @@ Section "${PRODUCT} (required)"
> > File "${SRCDIR}\Changelog"
> > File "${SRCDIR}\COPYING"
> > File "${SRCDIR}\COPYING.LIB"
> > - File "${SRCDIR}\README"
> > + File "${SRCDIR}\README.md"
> > File "${SRCDIR}\VERSION"
> >
> > File "${BINDIR}\*.bmp"
> > @@ -206,7 +206,7 @@ Section "Uninstall"
> > Delete "$INSTDIR\Changelog"
> > Delete "$INSTDIR\COPYING"
> > Delete "$INSTDIR\COPYING.LIB"
> > - Delete "$INSTDIR\README"
> > + Delete "$INSTDIR\README.md"
> > Delete "$INSTDIR\VERSION"
> > Delete "$INSTDIR\*.bmp"
> > Delete "$INSTDIR\*.bin"
> > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> > index afa7f79..8247305 100755
> > --- a/scripts/checkpatch.pl
> > +++ b/scripts/checkpatch.pl
> > @@ -286,7 +286,7 @@ sub top_of_kernel_tree {
> >
> > my @tree_check = (
> > "COPYING", "MAINTAINERS", "Makefile",
> > - "README", "docs", "VERSION",
> > + "README.md", "docs", "VERSION",
> > "vl.c"
> > );
>
> Does raise the question of whether we should be renaming
> the file in the first place. README is the traditional
> name and fits with all our other basically-plain-text
> document names like COPYING, MAINTAINERS, HACKING.
As mentioned in my original review, we could just create a symlink
between READE & README.md or vica-verca if we wish to preserve the
"normal" filename, but still have github do its magic.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2016-07-20 8:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 17:47 [Qemu-devel] [PATCH] Fix regressions caused by renaming README Stefan Weil
2016-07-19 18:15 ` Pranith Kumar
2016-07-19 20:53 ` Peter Maydell
2016-07-19 21:17 ` Pranith Kumar
2016-07-19 21:33 ` Peter Maydell
2016-07-20 6:37 ` Markus Armbruster
2016-07-20 7:00 ` Paolo Bonzini
2016-07-20 7:07 ` Fam Zheng
2016-07-20 7:09 ` Paolo Bonzini
2016-07-20 7:18 ` Fam Zheng
2016-07-20 8:47 ` Daniel P. Berrange [this message]
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=20160720084713.GE29602@redhat.com \
--to=berrange@redhat.com \
--cc=bobby.prani@gmail.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sw@weilnetz.de \
/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.