From: Holger Freyther <zecke@selfish.org>
To: openembedded-devel@lists.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: Sat, 31 Jan 2009 20:36:59 +0100 [thread overview]
Message-ID: <200901312037.00579.zecke@selfish.org> (raw)
In-Reply-To: <c384c5ea0812030846n604eccf0pe47d15f7122f0435@mail.gmail.com>
On Wednesday 03 December 2008 17:46:04 Leon Woestenberg 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.
>
> Does this make sense?
Yes it does, but I'm also toying with the idea of turning everything into a
git checkout (using git am for the patches...)...
z.
prev parent reply other threads:[~2009-01-31 19:47 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
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 [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=200901312037.00579.zecke@selfish.org \
--to=zecke@selfish.org \
--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.