From: Tom Rini <trini@kernel.crashing.org>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch
Date: Wed, 3 Dec 2008 10:51:43 -0700 [thread overview]
Message-ID: <20081203175143.GK16628@smtp.west.cox.net> (raw)
In-Reply-To: <b6ebd0a50812030900r593d6bb0me3a35316907b21ab@mail.gmail.com>
On Wed, Dec 03, 2008 at 10:00:13AM -0700, Chris Larson wrote:
> On Wed, Dec 3, 2008 at 9:46 AM, Leon Woestenberg
> <leon.woestenberg@gmail.com> wrote:
> > Hello,
> >
> > during maintenance of our local set of OE patches, it would be handy
> > not having to copy patches back into the repository.
> >
> > i.e. the patch fetcher could instead of copy the patch to the work
> > directory, soft-link from the repo.
>
> I can see why you want it. The file:// fetcher copies everything,
> not just patches, they aren't fetched differently currently. You
> could introduce regressions if it were to affect anything but patches,
> so you'd have to add a special case for uris with patch=1 in the
> file:// fetcher to link instead of copy, and possibly make it optional
> via a variable. I take it you do a lot of patch alterations in the
> workdir to fix problems?
A lot? No. But for everyone working from a fixed OE snapshot, this
would be a nice timesaver. Heck, soft-linking all of the file URIs
would be nice here. Perhaps a variable to control doing it always
(default to off) ?
--
Tom Rini
next prev parent reply other threads:[~2008-12-03 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 16:46 [RFC Wild Ideas Department] create soft-links from <pkg>/<src>/patches/some_local.patch to <oe.git>/packages/<pkg>/files/some_local.patch Leon Woestenberg
2008-12-03 17:00 ` Chris Larson
2008-12-03 17:51 ` Tom Rini [this message]
2008-12-03 19:49 ` Khem Raj
2008-12-03 20:00 ` Leon Woestenberg
2008-12-04 16:40 ` Robert Schuster
2009-01-31 19:36 ` Holger 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=20081203175143.GK16628@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox