From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 2/3] mtools: don't install-info; fixes build on non-Debian hosts
Date: Tue, 18 Aug 2009 12:35:57 +0200 [thread overview]
Message-ID: <h6e06e$h0m$2@ger.gmane.org> (raw)
In-Reply-To: <be7a9f3d0908180202t125e5c21tf77ed80c0ab07d22@mail.gmail.com>
On 18-08-09 11:02, Otavio Salvador wrote:
> Hello Holger,
>
> On Mon, Aug 17, 2009 at 11:11 AM, Holger Hans Peter
> Freyther<holger+oe@freyther.de> wrote:
>> again, no need to bump the PR.
>
> I completely disagree with changes landing without PR bump.
>
> Not bumping them can cause a change, that breaks something, to not be
> noticed for long time.
>
> In my opinion we ought to _always_ bump PR when changing the recipe.
> This ensure it is widely tested and deployed.
It also makes it easier to spot patterns in tinderbox.
regards,
Koen
next prev parent reply other threads:[~2009-08-18 10:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 13:29 [PATCH 1/3] nasm: fix COMPATIBLE_HOST to match any vendor Michael Smith
2009-08-17 13:29 ` [PATCH 2/3] mtools: don't install-info; fixes build on non-Debian hosts Michael Smith
2009-08-17 13:29 ` [PATCH 3/3] syslinux: upgrade to 3.82 and split into a few packages Michael Smith
2009-08-17 14:12 ` Holger Hans Peter Freyther
2009-08-17 15:35 ` Michael Smith
2009-08-17 18:29 ` Roman I Khimov
2009-08-17 18:45 ` Michael Smith
2009-08-18 9:04 ` Roman I Khimov
2009-08-18 18:15 ` x86_64 multilib Michael Smith
2009-08-18 19:42 ` Roman I Khimov
2009-08-19 12:35 ` [PATCH 3/3] syslinux: upgrade to 3.82 and split into a fewPackages marcin
2009-08-17 14:11 ` [PATCH 2/3] mtools: don't install-info; fixes build on non-Debian hosts Holger Hans Peter Freyther
2009-08-18 9:02 ` Otavio Salvador
2009-08-18 10:35 ` Koen Kooi [this message]
2009-08-18 13:55 ` Michael Smith
2009-08-17 14:09 ` [PATCH 1/3] nasm: fix COMPATIBLE_HOST to match any vendor Holger Hans Peter Freyther
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='h6e06e$h0m$2@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.