unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: "Joseph S. Myers" <joseph@codesourcery.com>,
	 Andreas Schwab <schwab@suse.de>,
	 Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	 Szabolcs Nagy <szabolcs.nagy@arm.com>,
	 GNU C Library <libc-alpha@sourceware.org>
Subject: Re: Changes to "Contribution Checklist" -- Format of the contribution.
Date: Thu, 14 Feb 2019 10:58:25 +0100	[thread overview]
Message-ID: <87y36iy9mm.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <187fa6e8-11fc-e33a-daa1-51d0aa3962f7@redhat.com> (Carlos O'Donell's message of "Wed, 13 Feb 2019 16:33:10 -0500")

* Carlos O'Donell:

> I would like to propose that the "Contribution Checklist"
> tell first time developers to send a 'git format-patch'
> file or inlined text to the list for patch review instead
> of a split patch and distinct ChangeLog.

I would like to see the actual wording.

Should we move the contribution checklist to Git, so that it we can
maintain it more easily?

Perhaps not into the manual, where it become outdated after
installation, but somewhere else in the tree?

Thanks,
Florian

  parent reply	other threads:[~2019-02-14  9:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13 21:33 Changes to "Contribution Checklist" -- Format of the contribution Carlos O'Donell
2019-02-13 22:19 ` Paul Eggert
2019-02-13 23:00 ` Joseph Myers
2019-02-14  0:11   ` Carlos O'Donell
2019-02-14  1:38     ` Joseph Myers
2019-02-14  9:58 ` Florian Weimer [this message]
2019-02-14 17:32   ` Joseph Myers
2019-02-15 11:54     ` Florian Weimer
2019-02-14 20:17   ` Carlos O'Donell
2019-02-15 12:41     ` Florian Weimer
2019-02-15 13:53       ` Joseph Myers
2019-03-13 15:47         ` Florian Weimer
2019-03-13 21:35           ` Joseph Myers
2019-03-13 21:40             ` Carlos O'Donell
2019-03-13 22:02               ` Florian Weimer
2019-03-24 17:18                 ` Gabriel F. T. Gomes
2019-03-13 21:54             ` Florian Weimer
2019-03-13 18:22       ` Carlos O'Donell

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=87y36iy9mm.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@suse.de \
    --cc=szabolcs.nagy@arm.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 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).