From: Mike Frysinger <vapier@gentoo.org>
To: Fred Cooke <fred.cooke@gmail.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>,
binutils <binutils@sourceware.org>
Subject: Re: small request regarding commits in binutils-gdb.git
Date: Thu, 16 Jan 2014 02:41:00 -0000 [thread overview]
Message-ID: <201401152141.38850.vapier@gentoo.org> (raw)
In-Reply-To: <CABZhLO8Kg_RgXGADyKPB15hFE5stZsxyVhN87mhyyX=s5RAkKA@mail.gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 616 bytes --]
On Wednesday 15 January 2014 20:41:16 Fred Cooke wrote:
> Fair call, though the commit message format requirements might become
> a bit onerous if done this way, OR, generation might generate quite a
> few errors/misprints. I guess the rate of commits is pretty low, and
> commit size pretty big, on average, for binutils, though.
commit message format isn't really any more onerous than maintaining a
ChangeLog file by hand
i don't know how other projects handle typos/updates. maybe they just live
with them. i haven't looked too closely at the scripts in use, but should be
easy to ask.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-01-16 2:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 12:12 Joel Brobecker
2014-01-15 15:28 ` Mike Frysinger
2014-01-15 15:51 ` Tom Tromey
2014-01-15 16:04 ` Eli Zaretskii
2014-01-15 16:25 ` Joel Brobecker
2014-01-15 16:57 ` Eli Zaretskii
2014-01-15 17:12 ` Mike Frysinger
2014-01-15 19:48 ` Fred Cooke
2014-01-15 20:02 ` Mike Frysinger
2014-01-15 20:38 ` Eli Zaretskii
2014-01-15 20:57 ` Mike Frysinger
2014-01-15 21:09 ` Eli Zaretskii
2014-01-16 2:11 ` Alan Modra
2014-01-16 2:17 ` Joel Brobecker
2014-01-16 1:41 ` Fred Cooke
2014-01-16 2:41 ` Mike Frysinger [this message]
2014-01-15 16:50 ` Pedro Alves
2014-01-15 17:03 ` Tom Tromey
2014-01-15 18:07 ` Gary Benson
2014-01-16 11:41 ` Jose E. Marchesi
2014-01-15 19:31 ` Cary Coutant
2014-01-15 19:45 ` Tom Tromey
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=201401152141.38850.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=binutils@sourceware.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=fred.cooke@gmail.com \
--cc=gdb-patches@sourceware.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