From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] hddtemp: add from OE-Classic and update
Date: Sat, 20 Oct 2012 14:31:57 +0100 [thread overview]
Message-ID: <5449472.OOgUu9G1KU@helios> (raw)
In-Reply-To: <CAP9ODKruOzzkoRVKcCSRUe6Rmnhh+++gDNEYGOf8-GSuw0b5Ug@mail.gmail.com>
On Saturday 20 October 2012 10:13:50 Otavio Salvador wrote:
> On Sat, Oct 20, 2012 at 9:22 AM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
> > On Saturday 20 October 2012 08:54:37 Otavio Salvador wrote:
> >> I think some patches could be cleaned up. Specially the generated
> >> files. Debian includes them in the patch and the packaging guide
> >> advices to do it (there're reasons for it) but OE regenerated those so
> >> I think it could be dropped.
> >
> > I'd really rather not touch the content of the patches - hddtemp upstream
> > is dead, we're not intending to maintain our own fork and it's easier if
> > we can just pull in any new patches as-is from Debian or Fedora (with
> > source information, which I did add to the top of each patch).
>
> Right but including generated files is waste of space, unpack time and
> patching time. We're rewrite those in do_configure.
So leaving aside the tiny amount of time/space we're talking about for a
second, which files are you referring to exactly?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-10-20 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 16:46 [meta-oe][PATCH] hddtemp: add from OE-Classic and update Paul Eggleton
2012-10-20 11:54 ` Otavio Salvador
2012-10-20 12:22 ` Paul Eggleton
2012-10-20 13:13 ` Otavio Salvador
2012-10-20 13:31 ` Paul Eggleton [this message]
2012-10-20 15:07 ` Otavio Salvador
-- strict thread matches above, loose matches on Subject: below --
2012-10-20 11:25 Paul Eggleton
2012-10-20 11:41 ` Otavio Salvador
2012-10-18 17:40 Paul Eggleton
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=5449472.OOgUu9G1KU@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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.