From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: Gary Benson <gbenson@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Descriptive subjects
Date: Fri, 15 May 2015 20:01:00 -0000 [thread overview]
Message-ID: <20150515200116.GA14956@adacore.com> (raw)
In-Reply-To: <20150515122844.GK4767@adacore.com>
> +1. In fact, I would even suggest that we follow that guideline
> for revision logs as well. When going through the log trying to
> identify the commits that might be responsible for a change in
> behavior, "PR bla/12345" is not very helpful for that.
Something that occured to me a little after I sent the email:
I suspect that using the PR's subject would often work as a good
subject for the commit.
--
Joel
next prev parent reply other threads:[~2015-05-15 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 7:59 Gary Benson
2015-05-15 11:37 ` Pedro Alves
2015-05-15 12:28 ` Joel Brobecker
2015-05-15 20:01 ` Joel Brobecker [this message]
2015-05-15 17:32 ` Patrick Palka
2015-05-15 18:38 ` Doug Evans
2015-05-15 18:40 ` Doug Evans
2015-05-18 9:10 ` Gary Benson
2015-05-18 20:25 ` Doug Evans
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=20150515200116.GA14956@adacore.com \
--to=brobecker@adacore.com \
--cc=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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