From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Carlos O'Donell <carlos@redhat.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
<libc-alpha@sourceware.org>
Subject: Re: When can we stop writing ChangeLogs?
Date: Mon, 30 Sep 2019 19:41:32 +0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1909301935210.1462@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87ftkdzl4v.fsf@oldenburg2.str.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
On Mon, 30 Sep 2019, Florian Weimer wrote:
> I'm looking for something far simpler here—a script that submitters and
> reviewers can run to see what's going to be committed, and some level of
> project consensus that this is how patches should be posted.
I suggest that should be "git am", as an existing known format for email
patch submissions, for any case except where the patch has already been
committed (and really "git am" format could probably be used there as
well), the patch would be excessively large (whether because of large
generated files or otherwise) or the patch contains mixed character sets
which require it to be attached in compressed form to avoid it being
mangled. We can discuss details regarding e.g. scissors lines, but I
think we should still aim for patch submissions that are valid for "git
am" in some form - and in particular, that use "git am" markings to
separate the commit message from other remarks (e.g. differences between
revisions of the patch) that are not intended as part of the commit
message.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2019-09-30 19:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 18:55 When can we stop writing ChangeLogs? Siddhesh Poyarekar
2019-09-24 23:21 ` Adhemerval Zanella
2019-09-28 3:16 ` Carlos O'Donell
2019-09-30 14:30 ` Siddhesh Poyarekar
2019-09-30 15:56 ` Florian Weimer
2019-09-30 16:56 ` Siddhesh Poyarekar
2019-09-30 18:36 ` Florian Weimer
2019-09-30 19:27 ` Siddhesh Poyarekar
2019-09-30 19:42 ` Florian Weimer
2019-10-04 1:37 ` Gabriel F. T. Gomes
2019-10-07 2:27 ` Carlos O'Donell
2019-10-07 9:05 ` Florian Weimer
2019-10-07 9:40 ` Maciej W. Rozycki
2019-10-07 9:47 ` Florian Weimer
2019-09-30 19:31 ` Carlos O'Donell
2019-09-30 19:39 ` Siddhesh Poyarekar
2019-09-30 19:41 ` Joseph Myers [this message]
2019-09-30 19:53 ` Carlos O'Donell
2019-10-01 17:41 ` Florian Weimer
2019-10-01 20:18 ` Joseph Myers
2019-10-02 9:30 ` Florian Weimer
2019-09-30 19:52 ` Maciej W. Rozycki
2019-10-07 12:56 ` Florian Weimer
2019-10-07 13:31 ` Florian Weimer
2019-10-07 14:49 ` Siddhesh Poyarekar
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.1909301935210.1462@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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 read-only IMAP folder(s) and NNTP newsgroup(s).