From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: "openembedded-devel@lists.openembedded.org"
<openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-webserver][PATCH 0/6] Add meta-webserver
Date: Wed, 03 Oct 2012 12:29:56 +0100 [thread overview]
Message-ID: <2386446.3zWsEst4ZG@helios> (raw)
In-Reply-To: <8B480455-60FE-418C-9A98-DB281B347CE2@dominion.thruhere.net>
On Wednesday 03 October 2012 13:27:41 Koen Kooi wrote:
> Op 3 okt. 2012 om 12:43 heeft Paul Eggleton <paul.eggleton@linux.intel.com>
het volgende geschreven:
> > On Wednesday 03 October 2012 12:24:19 Koen Kooi wrote:
> >> Squash those "import" with the "fix" commits, no sense in having a broken
> >> recipe in there.
> >
> > I'd rather not - there is sense in being clear about the changes, because
> > there are a large number of them in this case.
>
> The broken recipes are still available in OE classic if people want to
> compare them. I still don't get why you want to have broken recipes in the
> tree at multiple points in your series.
Because I want to easily see in "git blame" where particular lines came from -
did I add them, or have they been around for ages?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-10-03 11:42 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-01 16:14 [meta-webserver][PATCH 0/6] Add meta-webserver Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 1/6] Add meta-webserver layer Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 2/6] apache2: add from OE-Classic Paul Eggleton
2012-10-03 10:17 ` Koen Kooi
2012-10-03 11:28 ` Paul Eggleton
2012-10-03 11:41 ` Koen Kooi
2012-10-03 12:23 ` Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 3/6] modphp: " Paul Eggleton
2012-10-03 10:20 ` Koen Kooi
2012-10-03 11:28 ` Paul Eggleton
2012-10-03 11:44 ` Koen Kooi
2012-10-01 16:14 ` [meta-webserver][PATCH 4/6] apache2: update to version 2.4.2 and fix Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 5/6] modphp: update to 5.3.14 " Paul Eggleton
2012-10-01 16:14 ` [meta-webserver][PATCH 6/6] xdebug: add new recipe Paul Eggleton
2012-10-03 10:21 ` Koen Kooi
2012-10-03 11:28 ` Paul Eggleton
2012-10-03 11:47 ` Koen Kooi
2012-10-03 13:08 ` Paul Eggleton
2012-10-02 14:40 ` [meta-webserver][PATCH 0/6] Add meta-webserver Koen Kooi
2012-10-02 14:53 ` Paul Eggleton
2012-10-03 10:24 ` Koen Kooi
2012-10-03 10:43 ` Paul Eggleton
2012-10-03 11:27 ` Koen Kooi
2012-10-03 11:29 ` Paul Eggleton [this message]
2012-10-03 11:43 ` Koen Kooi
2012-10-03 12:23 ` Paul Eggleton
2012-10-03 13:12 ` Koen Kooi
2012-10-03 13:43 ` Paul Eggleton
2012-10-03 14:08 ` McClintock Matthew-B29882
2012-10-03 14:18 ` Paul Eggleton
2012-10-03 14:19 ` Khem Raj
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=2386446.3zWsEst4ZG@helios \
--to=paul.eggleton@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--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.