From: Klaus Schwarzkopf <schwarzkopf@sensortherm.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] download link fixed
Date: Sat, 27 Nov 2010 11:27:59 +0100 [thread overview]
Message-ID: <4CF0DD2F.80102@sensortherm.de> (raw)
In-Reply-To: <20101127102332.GK22419@excalibur.local>
Hi Stefan,
ok, i try it on my next patch ;-)
Regards,
Klaus
Am 27.11.2010 11:23, schrieb Stefan Schmidt:
> Hello.
>
> On Sat, 2010-11-27 at 11:20, Klaus Schwarzkopf wrote:
>> Is this patch ok or what can i do better?
>
> You could do better, but already on the right way :)
>
> - The subject line does not mention which areas/recipes are touched.
> - Separate patches for separate recipes are better to track changes on recipe
> level.
>
> http://wiki.openembedded.org/index.php/Commit_Policy
>
> regards
> Stefan Schmidt
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2010-11-27 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 10:15 [PATCH] download link fixed Klaus Schwarzkopf
2010-11-27 10:20 ` Klaus Schwarzkopf
2010-11-27 10:23 ` Stefan Schmidt
2010-11-27 10:27 ` Klaus Schwarzkopf [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=4CF0DD2F.80102@sensortherm.de \
--to=schwarzkopf@sensortherm.de \
--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.