From: GNUtoo <GNUtoo@no-log.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: OE weekly changelog 2009-06-01 to 2009-06-08
Date: Thu, 11 Jun 2009 21:46:17 +0200 [thread overview]
Message-ID: <1244749582.13175.6.camel@port4> (raw)
In-Reply-To: <1244584036.5998.44.camel@dax.rpnet.com>
On Tue, 2009-06-09 at 22:47 +0100, Richard Purdie wrote:
> On Tue, 2009-06-09 at 23:16 +0200, GNUtoo wrote:
> > On Mon, 2009-06-08 at 17:46 +0200, Marcin Juszkiewicz wrote:
> > > Maybe will also teach contributors to write shorter summaries ;)
> > I often(but not always) write long summaries for giving info on why I
> > did it this way to it's easier to maintain...
> > So If it's better to write shorter summaries...where should I write the
> > long version?
>
> You write a short summary as the first line of your commit message and
> the longer description then goes underneath. Both are useful.
>
> Cheers,
>
> Richard
thanks a lot.
Denis.
next prev parent reply other threads:[~2009-06-11 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 14:59 OE weekly changelog 2009-06-01 to 2009-06-08 Cliff Brake
2009-06-08 15:46 ` Marcin Juszkiewicz
2009-06-09 21:16 ` GNUtoo
2009-06-09 21:47 ` Richard Purdie
2009-06-11 19:46 ` GNUtoo [this message]
2009-06-09 21:52 ` Leon Woestenberg
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=1244749582.13175.6.camel@port4 \
--to=gnutoo@no-log.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.