From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Re: A question of workflow
Date: Tue, 09 Jan 2007 13:54:11 +0100 [thread overview]
Message-ID: <eo039k$pe7$1@sea.gmane.org> (raw)
In-Reply-To: <1168279741.4526.12.camel@ip6-localhost>
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 one is also easy. They are the ones that quilt cannot
apply anymore when doing "quilt push -a" ;-)
next prev parent reply other threads:[~2007-01-09 12:56 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-30 5:16 A question of workflow Matthew Palmer
2006-12-30 19:19 ` Richard Purdie
2006-12-30 21:43 ` Matthew Palmer
2006-12-30 22:07 ` Koen Kooi
2006-12-30 23:08 ` Erik Hovland
2006-12-30 23:40 ` Matthew Palmer
2006-12-31 0:02 ` Richard Purdie
2006-12-31 9:36 ` Koen Kooi
2006-12-31 11:12 ` Matthew Palmer
2006-12-30 23:59 ` Matthew Palmer
2006-12-31 0:06 ` Richard Purdie
2006-12-31 9:45 ` Koen Kooi
2006-12-31 11:00 ` Matthew Palmer
2006-12-31 11:10 ` Koen Kooi
2007-01-07 20:04 ` Patrick Ohly
2007-01-07 21:16 ` Paul Sokolovsky
2007-01-07 21:40 ` Patrick Ohly
2007-01-07 22:03 ` Matthew Palmer
2007-01-07 22:46 ` Justin Patrin
2007-01-07 22:56 ` Matthew Palmer
2007-01-07 23:11 ` Justin Patrin
2007-01-08 18:28 ` Patrick Ohly
2007-01-08 19:11 ` Justin Patrin
2007-01-08 21:02 ` Patrick Ohly
2007-01-08 21:13 ` Koen Kooi
2007-01-08 21:43 ` Patrick Ohly
2007-01-08 21:53 ` Justin Patrin
2007-01-09 9:42 ` Richard Purdie
2007-01-09 19:51 ` Patrick Ohly
2007-01-08 1:18 ` Rolf Leggewie
2007-01-08 18:09 ` Patrick Ohly
2007-01-09 12:51 ` Rolf Leggewie
2007-01-09 12:54 ` Rolf Leggewie [this message]
2007-01-09 19:39 ` Patrick Ohly
2007-01-02 20:06 ` Paul Sokolovsky
2007-01-02 20:08 ` [Angstrom-devel] " Koen Kooi
2007-01-04 4:23 ` Justin Patrin
2006-12-31 2:41 ` jack-oe
2007-01-02 0:05 ` Cliff Brake
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='eo039k$pe7$1@sea.gmane.org' \
--to=no2spam@nospam.arcornews.de \
--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 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.