From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Lynn Lin : Signed-off-by: Khem Raj <raj.khem@gmail.com>
Date: Thu, 19 Feb 2009 20:43:56 -0800 [thread overview]
Message-ID: <20090220044356.GA31015@gmail.com> (raw)
In-Reply-To: <c384c5ea0902161127y3a2d7312j5cd9c6ceae304677@mail.gmail.com>
On (16/02/09 20:27), Leon Woestenberg wrote:
> Hello,
>
> On Sun, Feb 15, 2009 at 7:21 PM, Marcin Juszkiewicz
> <openembedded@haerwu.biz> wrote:
> > On Sunday 15 of February 2009 03:35:49 GIT User account wrote:
> >> Author: Lynn Lin <lynn.lin@avocent.com>
> >> Date: Sat Feb 14 18:35:07 2009 -0800
> >>
> >> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> >>
> >> mini-httpd: New recipe.
> >
> > WTF? Please conform to CommitPolicy (first line is summary of commit).
Dont fret :).
Well in theory summary of commit could be adding new recipe. What were
you expecting in first line for a new recipe.
However I think I could have provided more lines with a bit more details.
> >
> Please watch your language. I know the choice of abbreviation isn't
> meant to be rude, but that doesn't rectify it.
>
> This might be Khem re-using his existing work flow and tools for
> handling patches.
>
> Khem, could you pls adapt your workflow a bit; we like our commit msg
> in a certain manner; see wiki CommitPolicy.\
yes. I will.
>
> Thanks,
> --
> Leon
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2009-02-20 4:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090215023549.92DE8E802F@amethyst.openembedded.net>
2009-02-15 18:21 ` [oe-commits] Lynn Lin : Signed-off-by: Khem Raj <raj.khem@gmail.com> Marcin Juszkiewicz
2009-02-16 19:27 ` Leon Woestenberg
2009-02-20 4:43 ` Khem Raj [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=20090220044356.GA31015@gmail.com \
--to=raj.khem@gmail.com \
--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.