[oe] A question of workflow
Patrick Ohly
Patrick.Ohly at gmx.de
Tue Jan 9 19:39:09 UTC 2007
On Tue, 2007-01-09 at 13:54 +0100, Rolf Leggewie wrote:
> Patrick Ohly wrote:
> > * you have to keep track of which patches have been applied, and
> > you cannot let tools do it for you
>
> Did you mean you wanted to know which of your patches have been applied
> in OE?
That's indeed what I meant. Just like quilt, patcher also keeps track of
which patches are currently applied locally.
> That one is also easy. They are the ones that quilt cannot
> apply anymore when doing "quilt push -a" ;-)
Not necessarily. The patch might also fail to apply because unrelated
changes were made upstream, so the external contributor always has to
check these conflicts manually.
On Tue, 2007-01-09 at 13:51 +0100, Rolf Leggewie wrote:
> > * you cannot easily(*) find out how your patch was modified after
> > you submitted it; this implies that learning how to write better
> > patches requires extra effort and thus becomes harder (more
> > unlikely?) and that mistakes made by the core developer when
> > merging the patch might not be detected by the external
> > developer (hey, it might happen, so for the sake of the argument
> > bear we me when I mention it ;-)
>
> This one is a little bit more work but still doable.
Of course, and if there is no better solution I don't mind doing it. But
that doesn't mean that one shouldn't at least search for a better
solution. Too bad there doesn't seem to be any :-/
--
Bye, Patrick Ohly
--
Patrick.Ohly at gmx.de
http://www.estamos.de/
More information about the Openembedded-devel
mailing list