From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Patches to svn based recipes
Date: Tue, 16 Oct 2007 18:09:35 +0200 [thread overview]
Message-ID: <4714E23F.4060402@student.utwente.nl> (raw)
In-Reply-To: <JQ09JU$226B655F90BD312D7F024131EBD56EA2@scarlet.be>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Philippe De Swert schreef:
> Hi all!
>
>
>> Could people please stop doing stuff like:
>>
>> openmoko-panel-bt_svn.bb: Drop panel-bluetooth.patch, as it was applied upstream
>> # delete "packages/openmoko-panel-plugins/files/panel-bluetooth.patch"
>>
>> openmoko-dialer2_svn.bb : patch is now applied upstream
>> - -SRC_URI += "file://openmoko-dialer.patch;patch=1"
>>
>> matchbox-keyboard: Bump svn revision and remove some patches in the bb file
>> since these patches were applied upstream.
>> - - file://matchbox-keyboard-applet.patch;patch=1;pnum=0 \
>> - - file://matchbox-keyboard-hide-delay.patch;patch=1"
>>
>> And use ;minrev= and ;maxrev=. Removing patches makes regression testing and
> building
>> older versions impossible.
>
> Ok. So all those things are forbidden. Good. So what are we expected to write
> in the commit message then?
Write what you want in the commit message, as long as you update the SRC_URI to use
;minrev= and ;maxrev=
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFHFOI/MkyGM64RGpERAvwmAKCDYxlc2fi/PWu2VI2KUu1/+GLI+QCeIWML
c6rJKitTc4u90z2FiSbQt44=
=vqS+
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-10-16 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 13:02 Patches to svn based recipes Philippe De Swert
2007-10-16 15:32 ` Marcin Juszkiewicz
2007-10-16 16:09 ` Koen Kooi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-16 11:05 Koen Kooi
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=4714E23F.4060402@student.utwente.nl \
--to=k.kooi@student.utwente.nl \
--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