From: dick.r.chiang@gmail.com
To: "Óscar Fuentes" <ofv@wanadoo.es>
Cc: emacs-devel@gnu.org
Subject: Re: Submitting patches from magit
Date: Fri, 20 Dec 2019 13:29:11 -0500 [thread overview]
Message-ID: <87v9qa4zrc.fsf@dick> (raw)
In-Reply-To: <87o8w4f52t.fsf@telefonica.net> ("Óscar Fuentes"'s message of "Thu, 19 Dec 2019 21:11:54 +0100")
ÓF> What about putting the changelog entry on the commit message?
Hum, I just read this tribal knowledge
https://lists.gnu.org/archive/html/emacs-devel/2019-09/msg00667.html
describing an "insider's" approach to changelog entries.
I suppose those who have commit rights find this method none too onerous.
As an "outsider" with a multi-file changeset, I've found wrangling changelog
entries for email submission tedious and highly error-prone.
A recent brouhaha discussing debbugs versus gitlab might also
have critiqued patch-based versus pull-request based development models, and
the efficacy of changelog entries. It's the kind of thing that has been so
meticulously maintained for so many years that the old guard cannot be
faulted for wanting to preserve forevermore. New-schoolers might counter with
the sunk-cost fallacy argument, however.
next prev parent reply other threads:[~2019-12-20 18:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 19:49 Submitting patches from magit dick.r.chiang
2019-12-19 20:06 ` Jonas Bernoulli
2019-12-19 20:25 ` Jonas Bernoulli
2019-12-19 20:11 ` Óscar Fuentes
2019-12-20 18:29 ` dick.r.chiang [this message]
2019-12-20 19:18 ` Óscar Fuentes
2019-12-20 19:51 ` dick.r.chiang
2019-12-20 21:26 ` Alan Third
2019-12-19 20:29 ` Phil Sainty
2019-12-19 20:41 ` dick.r.chiang
2019-12-19 22:24 ` Jonas Bernoulli
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v9qa4zrc.fsf@dick \
--to=dick.r.chiang@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).