All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: rename files dirs
Date: Mon, 16 Aug 2010 22:11:08 +0200	[thread overview]
Message-ID: <20100816201108.GI10076@jama> (raw)
In-Reply-To: <AANLkTi=XK3Le8ERWqmMt2DEVX3K4n=ua0Zdyu6qEOUcw@mail.gmail.com>

On Mon, Aug 16, 2010 at 10:00:42PM +0200, Frans Meulenbroeks wrote:
> Currently lots of our patches reside in a directory called files.
> Somewhere in the past koen explained me that that is not really proper
> (and I agree with them).
> files should only be used in case a dir has multiple recipes (say X.bb
> and Y.bb) which both use the same patch
> If there is only a single recipe with multiple versions (e.g.X_0.bb
> and X_1.bb) then common patches should go into a dir X.
> And if the patches are for a specific version they should go in X-0, X-1 etc.
> 
> When I'm bored again on a rainy sunday afternoon or so, I can spent
> some time on moving things.
> Are people comfortable with that?
> Also what would be the preferred way to store the patches for a recipe
> with only one version (Z_3.bb)
> Should this preferably be in Z or in Z-3 ?

If it's something where you expect the need to update the patch for Z_4
then I would say Z-3, but if it's some tweak (ie to allow crossbuilding)
and the same patch applied to Z_[12345] then Z is right dir (if Z_6
needs updated patch it will be named the same but in Z-6).
> 
> Your opinion is apprecated

I did exactly the same while cleaning xorg-* dirs. So I agree.

Regards,

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com



  reply	other threads:[~2010-08-16 20:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16 20:00 rename files dirs Frans Meulenbroeks
2010-08-16 20:11 ` Martin Jansa [this message]
2010-08-17  8:39 ` Dr. Michael Lauer
2010-08-17  8:55   ` Koen Kooi
2010-08-17  9:38     ` Dr. Michael Lauer

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=20100816201108.GI10076@jama \
    --to=martin.jansa@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.