From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel@gnu.org
Subject: Re: Your commit 7409a79
Date: Wed, 10 Dec 2014 03:26:39 -0600 [thread overview]
Message-ID: <85388n97ow.fsf@stephe-leake.org> (raw)
In-Reply-To: <83mw6wwyl8.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 09 Dec 2014 18:57:07 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> > CONTRIBUTE: Moved from etc/CONTRIBUTE.
>> >
>> > This is in preparation for restructuring of developer contribution
>> > documents; see http:/<archive reference> for the related discussion,
>> > and see http:/<archive reference> for the decision to move the file.
>> >
>> > This has a short summary line which tells enough in "git log" short
>> > formats, and then the details below, including the rationale.
>> >
>> > But this all is a creative, stylistic issue, not something to be
>> > codified in mandatory documents. There is no single solution to this;
>> > as long as people choose a reasonable one, and don't goof with
>> > misspellings or missing punctuation, they should be OK.
>
>> It's a big stretch to go from the examples in the Gnu coding standards
>> to this example. There are some like this in ./Changelog; first one
>> 2014-11-11 Eric S. Raymond <address@hidden>, and that has a leading
>> asterisk on the first line.
>
> Asterisks come from add-change-log-entry and friends, so it will not
> be there if you just write free text, like I did above.
> In any case, the asterisks are optional, IMO.
http://www.gnu.org/prep/standards/html_node/Change-Log-Concepts.html
last paragraph says asterisks are part of the required Changelog style.
> From experience, the rules are not rigid.
True, they are not consistently enforced.
But a new developer needs a clear set of rules, so they know what they
need to change in their habits from other projects.
> You need to put the right information there, and make it in correct
> English, and that's about all that's really required. Beyond that,
> it's all about your perfectionism.
That is not the impression I get from the mentoring comments on this
list, and it is not what it says in CONTRIBUTE.
--
-- Stephe
next prev parent reply other threads:[~2014-12-10 9:26 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 8:56 Your commit 7409a79 Eli Zaretskii
2014-12-06 10:22 ` Andreas Schwab
2014-12-06 10:29 ` Eli Zaretskii
2014-12-06 10:32 ` Paul Eggert
2014-12-06 15:29 ` Yuri Khan
2014-12-06 23:01 ` Stefan Monnier
2014-12-06 16:14 ` Tom
2014-12-06 18:54 ` Eli Zaretskii
2014-12-06 22:43 ` Stephen Leake
2014-12-06 22:33 ` Stephen Leake
2014-12-07 3:52 ` Eli Zaretskii
2014-12-07 22:39 ` Stephen Leake
2014-12-08 1:57 ` Paul Eggert
2014-12-08 2:28 ` Stephen J. Turnbull
2014-12-08 15:58 ` Eli Zaretskii
2014-12-08 23:38 ` Stephen Leake
2014-12-08 15:58 ` Eli Zaretskii
2014-12-08 18:24 ` Paul Eggert
2014-12-08 15:51 ` Eli Zaretskii
2014-12-08 17:32 ` John Yates
2014-12-08 17:57 ` Eli Zaretskii
2014-12-08 18:14 ` Paul Eggert
2014-12-08 18:28 ` Eli Zaretskii
2014-12-08 18:37 ` Eli Zaretskii
2014-12-08 18:54 ` Paul Eggert
2014-12-08 19:00 ` Stefan Monnier
2014-12-08 18:54 ` John Yates
2014-12-08 23:27 ` Stephen Leake
2014-12-09 0:51 ` Thien-Thi Nguyen
2014-12-09 8:08 ` Stephen Leake
2014-12-09 9:36 ` Thien-Thi Nguyen
2014-12-09 16:57 ` Eli Zaretskii
2014-12-10 9:26 ` Stephen Leake [this message]
2014-12-10 16:17 ` Eli Zaretskii
2014-12-10 17:04 ` Stephen Leake
2014-12-10 18:02 ` Eli Zaretskii
2014-12-10 19:20 ` Paul Eggert
2014-12-07 5:45 ` Stephen J. Turnbull
2014-12-06 22:59 ` Stefan Monnier
2014-12-07 22:44 ` Stephen Leake
2014-12-07 23:28 ` Stefan Monnier
2014-12-08 9:34 ` Stephen Leake
2014-12-08 10:22 ` Thien-Thi Nguyen
2014-12-08 14:58 ` Stefan Monnier
2014-12-08 23:32 ` Stephen Leake
2014-12-09 11:00 ` Richard Stallman
2014-12-09 11:09 ` David Kastrup
2014-12-10 8:24 ` Richard Stallman
2014-12-10 17:05 ` Stephen Leake
2014-12-10 19:08 ` Stefan Monnier
2014-12-08 15:54 ` Eli Zaretskii
2014-12-08 23:33 ` Stephen Leake
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=85388n97ow.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.