Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Graeme Gregory" <dp@xora.org.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev python-pyqt: fix dbg packaging
Date: Mon, 16 Jul 2007 12:44:01 +0100	[thread overview]
Message-ID: <200707161244020000@086416296> (raw)


> Because it seems to be the standard?  Because ml5 would seem to suggest
> this is the fifth release from Mickey which in this case is not true?
> Because going from ml to r should not cause problems?

> Because of the reasons above I did not really see any need for
> discussion.  I somehow still don't.

because you are stepping on toes of one of the oldest oe devs while we are all out of contact on way to guadec.

Graeme




             reply	other threads:[~2007-07-16 11:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16 11:44 Graeme Gregory [this message]
2007-07-16 11:55 ` [oe-commits] org.oe.dev python-pyqt: fix dbg packaging Michael Krelin
     [not found] <E1IAEG0-00049a-H7@linuxtogo.org>
2007-07-16  6:27 ` Koen Kooi
2007-07-16 11:15   ` Rolf Leggewie

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=200707161244020000@086416296 \
    --to=dp@xora.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox