qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: John Snow <jsnow@redhat.com>
Cc: Laszlo Ersek <lersek@redhat.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	qemu devel list <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] a suggestion to place *.c hunks last in patches
Date: Fri, 2 Dec 2016 10:23:35 +0000	[thread overview]
Message-ID: <20161202102335.GC14548@stefanha-x1.localdomain> (raw)
In-Reply-To: <3c7b4731-f9a5-6594-eaba-ce73b622b564@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]

On Wed, Nov 30, 2016 at 03:48:01PM -0500, John Snow wrote:
> On 11/30/2016 07:03 AM, Laszlo Ersek wrote:
> > On 11/30/16 11:55, Gerd Hoffmann wrote:
> >> On Mi, 2016-11-30 at 11:08 +0100, Laszlo Ersek wrote:
> >>> Recent git releases support the diff.orderFile permanent setting.
> >>
> >> Cool.
> >>
> >>> configure
> >>> *Makefile*
> >>> *.json
> >>> *.txt
> >>> *.h
> >>> *.c
> >>
> >> I'd put *.txt to the head so doc updates come first.
> > 
> > Good idea, yes.
> > 
> >> Otherwise the order looks good to me.
> >>
> >> Want sent a patch?
> > 
> > What file for? :)
> > 
> > I've considered modifying
> > <http://wiki.qemu.org/Contribute/SubmitAPatch>, but that article is
> > humongous already.
> > 
> 
> <OFFTOPIC>
> 
> I am itching to split this article up.
> 
> It was a giant monolith when I found it, so I split it up into "phases"
> and added a TOC, but it's still too unapproachable.
> 
> I'm thinking _two_ articles:
> 
> (1) A quick and dirty checklist that people can reference for their
> first submissions to make sure they are in the correct universe when
> submitting a patch, written expressly to be easy to digest without being
> overwhelming, and

Sounds good.

Another option for making the first time contribution process easier is
to automate as many of the rules as possible.  Can some of it be
implemented in checkpatch.pl?  Are there git-hooks we should supply?

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  parent reply	other threads:[~2016-12-02 10:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 10:08 [Qemu-devel] a suggestion to place *.c hunks last in patches Laszlo Ersek
2016-11-30 10:55 ` Gerd Hoffmann
2016-11-30 12:03   ` Laszlo Ersek
2016-11-30 12:27     ` Fam Zheng
2016-12-02 10:15       ` Laszlo Ersek
2016-11-30 12:29     ` Gerd Hoffmann
2016-11-30 15:36       ` Laszlo Ersek
2016-11-30 20:48     ` John Snow
2016-11-30 21:54       ` Laszlo Ersek
2016-12-02 10:23       ` Stefan Hajnoczi [this message]
2016-11-30 15:08 ` Michael S. Tsirkin
2016-11-30 15:26   ` Laszlo Ersek
2016-11-30 18:31     ` Michael S. Tsirkin
2016-11-30 15:35 ` Stefan Hajnoczi
2016-11-30 15:41 ` Eric Blake
2016-11-30 20:02   ` Laszlo Ersek

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=20161202102335.GC14548@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=jsnow@redhat.com \
    --cc=kraxel@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 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).