From: Andreas Oberritter <obi@opendreambox.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Use of == in shell scripts
Date: Tue, 26 Oct 2010 17:47:36 +0200 [thread overview]
Message-ID: <4CC6F818.5010105@opendreambox.org> (raw)
In-Reply-To: <4CC6F440.10509@opendreambox.org>
On 10/26/2010 05:31 PM, Andreas Oberritter wrote:
> How about splitting it into 5 patches?
>
> - classes (7 files)
> - contrib (4 files)
> - recipes/*/*.bb (24 files)
> - recipes/*/*.inc (14 files)
> - other files in recipes except recipes/obsolete (11 files)
Or how about those 37 patches?
http://git.opendreambox.org/?p=obi/openembedded.git;a=shortlog;h=refs/heads/equality-operator
Rationale:
- bbclasses: 1 patch per file
- contrib and recipes: 1 patch per directory
Regards,
Andreas
next prev parent reply other threads:[~2010-10-26 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 15:31 Use of == in shell scripts Andreas Oberritter
2010-10-26 15:47 ` Andreas Oberritter [this message]
2010-10-26 16:29 ` Michael Smith
2010-10-26 23:36 ` Andreas Oberritter
2010-10-27 1:47 ` Mike Detwiler
2010-11-13 16:10 ` Andreas Oberritter
2010-11-14 23:40 ` Michael Smith
2010-10-26 15:51 ` Maupin, Chase
2010-10-26 16:03 ` Chris Larson
2010-10-26 16:11 ` Andreas Oberritter
2010-10-26 16:21 ` Michael Smith
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=4CC6F818.5010105@opendreambox.org \
--to=obi@opendreambox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox