From: Rob Landley <rob@landley.net>
To: Stefan Beller <stefanbeller@googlemail.com>
Cc: Jeff Garzik <jgarzik@pobox.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Rewrite Documentation/SubmittingPatches.
Date: Sun, 15 Jul 2012 15:59:16 -0500 [thread overview]
Message-ID: <50032F24.8050903@landley.net> (raw)
In-Reply-To: <CALbm-EY-4iQy3HYi4bYdLVsLyr+iDecTUsVt43+_Nf9v_rkTyw@mail.gmail.com>
On 07/13/2012 09:45 AM, Stefan Beller wrote:
> This updates the documentation on how to create patches and send
> these to the kernel mailing list.
>
> The documentation before was written in times before git was there,
> so the crafting of the patch needed to be done manually by diff -up
> in the right directory.
>
> This patch aims at simplifying the patch sending process, without
> breaking the output results.
This patch is whitespace damaged (wordwrapped at the @@ lines), which is
either ironic or unfortunate. (After Alanis Morisette, I can't tell
anymore.)
> A discussion can be found at
> https://plus.google.com/111049168280159033135/posts/ekAxK9achsA
>
> Signed-off-by: Stefan Beller <stefanbeller@googlemail.com>
> Acked-by: Jeff Garzik jgarzik@pobox.com
But other than that Jeff's objection was my big one, and that's
addressed in v2, so:
Acked-by: Rob Landley <rob@landley.net>
Rob
--
GNU/Linux isn't: Linux=GPLv2, GNU=GPLv3+, they can't share code.
Either it's "mere aggregation", or a license violation. Pick one.
next prev parent reply other threads:[~2012-07-16 3:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 11:51 [PATCH] Rewrite Documentation/SubmittingPatches Stefan Beller
2012-07-13 12:33 ` Borislav Petkov
2012-07-13 14:09 ` Jeff Garzik
2012-07-13 14:45 ` Stefan Beller
2012-07-15 20:59 ` Rob Landley [this message]
2012-07-16 6:20 ` Stefan Beller
2012-07-16 15:06 ` Randy Dunlap
2012-08-13 16:02 ` [PATCH v2] " Stefan Beller
2012-07-25 23:41 ` [PATCH] " Junio C Hamano
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=50032F24.8050903@landley.net \
--to=rob@landley.net \
--cc=jgarzik@pobox.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefanbeller@googlemail.com \
/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.