All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junqian Gordon Xu <xjqian@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: QA for intentionally unpackaged files
Date: Wed, 09 May 2007 05:48:33 -0500	[thread overview]
Message-ID: <4641A701.5000204@gmail.com> (raw)
In-Reply-To: <02827798.20070509123821@gmail.com>

Paul Sokolovsky wrote:
>
>         So, maybe "closer look" is indeed a solution here?
>
>   
>         Who exactly will go over all recipes and add such lines?
>
>   
>
>         No, thanks, it likely shouldn't dump them at all then.

I take it as to find an easy and uncumbersome way to take care of this. 
I don't think doing nothing at all is a good solution.

Gordon



      parent reply	other threads:[~2007-05-09 10:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09  2:25 QA for intentionally unpackaged files Junqian Gordon Xu
2007-05-09  9:38 ` Paul Sokolovsky
2007-05-09 10:31   ` Michael Krelin
2007-05-09 10:42     ` Koen Kooi
2007-05-09 10:57       ` Junqian Gordon Xu
2007-05-09 11:26         ` Koen Kooi
2007-05-09 11:37           ` Paul Sokolovsky
2007-05-09 11:51             ` Michael Krelin
2007-05-09 11:43       ` Michael Krelin
2007-05-09 10:48   ` Junqian Gordon Xu [this message]

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=4641A701.5000204@gmail.com \
    --to=xjqian@gmail.com \
    --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.