From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: TSC Meeting 7/1/2010
Date: Thu, 14 Jan 2010 20:42:21 -0500 [thread overview]
Message-ID: <20100115014221.GA9872@denix.org> (raw)
In-Reply-To: <ac9c93b11001140102j36e07ca9u7cb9ddc5a9770cd4@mail.gmail.com>
On Thu, Jan 14, 2010 at 10:02:57AM +0100, Frans Meulenbroeks wrote:
> I suggest to review the rules;. E.g. this one:
> # This should all be on one line and you should leave an empty line
> before any detailed commit information.
> Nice, but if you use git commit and enter your message empty lines are removed.
Not really. "git format-patch" and "git am" use the empty line separation to
determine, what becomes patch subject and what is patch description in the
body. So, the above rule/requirement is very correct. More on the topic:
http://progit.org/book/ch5-2.html#commit_guidelines
--
Denys
next prev parent reply other threads:[~2010-01-15 1:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 22:22 TSC Meeting 7/1/2010 Richard Purdie
2010-01-13 23:19 ` Koen Kooi
2010-01-14 9:02 ` Frans Meulenbroeks
2010-01-14 13:53 ` Philip Balister
2010-01-15 1:42 ` Denys Dmytriyenko [this message]
2010-01-15 7:41 ` Frans Meulenbroeks
2010-01-14 11:34 ` Mark Brown
2010-01-14 13:51 ` Guo Hongruan
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=20100115014221.GA9872@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.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 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.