From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Patch for libfann-2.0.0 recipe
Date: Fri, 19 Jun 2009 19:53:49 +0200 [thread overview]
Message-ID: <h1gjbd$qpu$1@ger.gmane.org> (raw)
In-Reply-To: <20090619174723.GR15477@smtp.west.cox.net>
On 19-06-09 19:47, Tom Rini wrote:
> I would have assumed that since changing a package without changing the
> PR can wreck havoc on public feeds you would be in favor of helping to
> keep those problems at bay.
Check contrib/angstrom/upload-packages.sh :) It won't upload any
duplicate filenames, so angstrom public feeds don't suffer from such
things (they did, that's why Graeme and I added that logic).
Anyway, if you aren't paying enough attention to bump PR, you shouldn't
be pushing that commit!
There are a lot more things that warrant attention than not including PR
= "r0" in the recipe, inheriting pkgconfig being one of them.
regards,
Koen
next prev parent reply other threads:[~2009-06-19 18:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 17:14 Patch for libfann-2.0.0 recipe Elvis Dowson
2009-06-16 18:27 ` Koen Kooi
2009-06-16 18:38 ` Philip Balister
2009-06-16 19:00 ` Elvis Dowson
2009-06-16 19:59 ` Philip Balister
2009-06-16 21:36 ` Koen Kooi
2009-06-17 4:43 ` Rolf Leggewie
2009-06-18 16:05 ` Elvis Dowson
2009-06-18 16:48 ` Koen Kooi
2009-06-18 16:52 ` Otavio Salvador
2009-06-18 17:52 ` Koen Kooi
2009-06-18 18:11 ` Philip Balister
2009-06-18 18:24 ` Koen Kooi
2009-06-18 23:05 ` Tom Rini
2009-06-19 1:28 ` Otavio Salvador
2009-06-19 8:06 ` Koen Kooi
2009-06-19 17:47 ` Tom Rini
2009-06-19 17:53 ` Koen Kooi [this message]
2009-06-18 18:09 ` Philip Balister
2009-06-18 18:14 ` Koen Kooi
2009-06-18 18:36 ` Elvis Dowson
2009-06-18 18:56 ` Philip Balister
2009-06-19 13:37 ` Philip Balister
2009-06-19 13:52 ` Elvis Dowson
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='h1gjbd$qpu$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.