[oe] [PATCH] New package: siproxd
Otavio Salvador
otavio at ossystems.com.br
Mon Feb 16 01:09:01 UTC 2009
Tom Rini <trini at kernel.crashing.org> writes:
> On Sun, Feb 15, 2009 at 03:23:25PM -0300, Otavio Salvador wrote:
>> Roman I Khimov <khimov at altell.ru> writes:
>>
>> > Marcin Juszkiewicz:
>> >> On Friday 13 of February 2009 22:35:13 Roman I Khimov wrote:
>> >> > diff --git a/packages/siproxd/siproxd.inc
>> >> >
>> >> > +RDEPENDS = "libosip2"
>> >> >
>> >> > diff --git a/packages/siproxd/siproxd_0.7.1.bb
>> >> >
>> >> > +PR = "r0"
>> >>
>> >> Drop those two lines. You should not add libs to RDEPENDS (OE takes care
>> >> of it) and "r0" is default PR value.
>> >
>> > OK.
>>
>> It would be quite nice if you could send a git exported patch since it
>> makes the life eaiser for anyone going to apply your commit (locally or
>> for pushing it) and also keeps the credit for you.
>>
>> If you doesn't know to do that, some guidance can be find at:
>>
>> http://www.kernel.org/pub/software/scm/git/docs/git-format-patch.html
>
> Maybe getting a little OT, but now that we're starting to use patchwork,
> maybe some comments to GitPhraseBook on how people should be using
> git format-patch for OE?
I fear I'm not the best person to do that since I'm far from a good
English writer.
Basically we could suggest following workflow for regular users:
- when going to make any change at OE, start a personal branch
$: git checkout -b local master
- HACK; HACK; commit
- once happy with the end result, export the patches to send by mail
$: git format-patch master..
- mail them to ml
$: git send-email 0001-... --to openembedded-devel at lists.openembedded.org
- go take a beer ;-)
Please someone translate it in something easy to understand :-)
--
Otavio Salvador O.S. Systems
E-mail: otavio at ossystems.com.br http://www.ossystems.com.br
Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br
More information about the Openembedded-devel
mailing list