Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] .gitignore: add /bitbake to the ignore list for external distributions
Date: Wed, 09 May 2012 15:21:55 +0100	[thread overview]
Message-ID: <1336573316.5602.68.camel@phil-desktop> (raw)
In-Reply-To: <1336571192-15711-1-git-send-email-jason.wessel@windriver.com>

On Wed, 2012-05-09 at 08:46 -0500, Jason Wessel wrote:
> External distributions based on the oe-core will typically include
> bitbake in the top level directory.  The idea is to make it easy
> for external distributions to easily assemble a distribution
> with a pristine version of oe-core, add avoid the git untracked messages:

Presumably any non-trivial external distribution is going to include
other metadata as well, in which case they're going to have to
edit .gitignore for themselves anyway.  So it doesn't really seem as
though having bitbake be mentioned there in oe-core buys much.

On the other hand, actually moving bitbake inside the oe-core repository
seems like an idea which might have some merit.  It's not obvious that
having it in its own tree really achieves anything other than making
release engineering slightly more difficult.

p.





  parent reply	other threads:[~2012-05-09 14:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 13:46 [PATCH] .gitignore: add /bitbake to the ignore list for external distributions Jason Wessel
2012-05-09 13:58 ` Koen Kooi
2012-05-09 14:07   ` Marko Lindqvist
2012-05-09 16:10     ` Philip Balister
2012-05-09 16:14       ` Jason Wessel
2012-05-10  5:26       ` Khem Raj
2012-05-09 14:15   ` Jason Wessel
2012-05-09 14:21 ` Phil Blundell [this message]
2012-05-09 14:45   ` Jason Wessel
2012-05-09 15:00     ` Koen Kooi
2012-05-09 15:54   ` Richard Purdie

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=1336573316.5602.68.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@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