From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-netifaces: change license file name
Date: Wed, 11 Mar 2015 22:13:42 +0100 [thread overview]
Message-ID: <874mprkzjt.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1426093924-30591-1-git-send-email-clayton.shotwell@rockwellcollins.com> (Clayton Shotwell's message of "Wed, 11 Mar 2015 12:12:04 -0500")
>>>>> "Clayton" == Clayton Shotwell <clayton.shotwell@rockwellcollins.com> writes:
> From: David Graziano <david.graziano@rockwellcollins.com>
> Change license file name from README to README.rst.
That's not really a good commit message. Commit messages should explain
WHY a change is made, not just WHAT the change is.
Committed with this reworded, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2015-03-11 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 17:12 [Buildroot] [PATCH] python-netifaces: change license file name Clayton Shotwell
2015-03-11 21:13 ` Peter Korsgaard [this message]
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=874mprkzjt.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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 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.