All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Commit message policy for new recipes
Date: Mon, 16 Feb 2009 20:51:08 -0500	[thread overview]
Message-ID: <499A180C.1070802@balister.org> (raw)
In-Reply-To: <499A0B64.2000303@whitby.id.au>

[-- Attachment #1: Type: text/plain, Size: 471 bytes --]

Rod Whitby wrote:
> <http://cia.vc/stats/project/openembedded/.message/efeb91>
> 
> Any chance the commit message policy could be changed such that commits
> for new recipes contain a description of the software that has been
> pacakaged?
> 
> Then someone following the commit RSS feed can see interesting new
> package descriptions ...

+1, in the future I'll try and give a one or two line description of the 
software when I commit new recipes.

Philip

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3303 bytes --]

  reply	other threads:[~2009-02-17  1:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17  0:57 Commit message policy for new recipes Rod Whitby
2009-02-17  1:51 ` Philip Balister [this message]
2009-02-19 18:23   ` Khem Raj
2009-02-19 20:00     ` GNUtoo
2009-02-17 19:32 ` Tim Ellis

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=499A180C.1070802@balister.org \
    --to=philip@balister.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.