From: Graeme Gregory <dp@xora.org.uk>
To: Paul Menzel <paulepanter@users.sourceforge.net>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] transmission: add recipe for 2.22 version
Date: Fri, 11 Mar 2011 15:15:47 +0000 [thread overview]
Message-ID: <4D7A3CA3.4040808@xora.org.uk> (raw)
In-Reply-To: <1299855298.4137.51.camel@mattotaupa>
On 11/03/2011 14:54, Paul Menzel wrote:
> Dear Graeme,
>
>
> Am Freitag, den 11.03.2011, 11:00 +0100 schrieb Paul Menzel:
>
>> Am Freitag, den 11.03.2011, 02:03 +0100 schrieb Lukas-David Gorris:
>>> Depends on the the previously sent libevent bump.
>> Using `git format-patch -2 -s` you can create patches where the
>> dependencies are shown in the subject, e. g. [PATCH 1/2] and [PATCH
>> 2/2].
>>
>>> From: Lukas-David Gorris <lukas.gorris@gmail.com>
>>> Date: Fri, 11 Mar 2011 02:00:56 +0100
>>> Subject: [oe] [PATCH] transmission: add recipe for 2.22 version
>> As already written in another thread, your MUA mangled the patches.
>> Please turn off automatic line wrapping (normal to preformatted) or
>> using `git send-email`.
>>
>> Your Signed-off-by line is also missing as demanded by the commit policy
>> [1].
>>
>> Secondly, I would appreciate if you could add to the commit message,
>> what build configuration you tested your new recipe/patch with and if
>> all operations worked when running it.
>>
>>> ---
>>> recipes/transmission/transmission_2.22.bb | 9 +++++++++
>>> 1 files changed, 9 insertions(+), 0 deletions(-)
>>> create mode 100644 recipes/transmission/transmission_2.22.bb
>>>
>>> diff --git a/recipes/transmission/transmission_2.22.bb
>>> b/recipes/transmission/transmission_2.22.bb
>>> new file mode 100644
>>> index 0000000..e9a7891
>>> --- /dev/null
>>> +++ b/recipes/transmission/transmission_2.22.bb
>>> @@ -0,0 +1,9 @@
>>> +require transmission.inc
>>> +
>>> +DEPENDS += "libevent"
>>> +
>>> +PR = ${INC_PR}.1
>> You should start at 0.
>>
>>> +SRC_URI[archive.md5sum] = "6499986bf769276310b00bda1090090d"
>>> +SRC_URI[archive.sha256sum] = "5a4079194f45260c143f21ea6f33ce2660d89fca02ad8f1e65169968d365e4d4"
> why did you commit in e124c44f [1] without my remarks being addressed?
> Also the things you put into the commit message could have been left
> out.
>
>
I got your comments long after I had already done the commits. Im
getting a lot of OE emails seriously delayed today.
I used pw-am as per the process recomended.
Graeme
next prev parent reply other threads:[~2011-03-11 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 1:03 [PATCH] transmission: add recipe for 2.22 version Lukas-David Gorris
2011-03-11 10:00 ` Paul Menzel
2011-03-11 14:54 ` Paul Menzel
2011-03-11 15:15 ` Graeme Gregory [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-03-11 1:06 Lukas-David Gorris
2011-03-11 10:08 ` Lukas-David Gorris
2011-03-11 12:15 ` Paul Menzel
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=4D7A3CA3.4040808@xora.org.uk \
--to=dp@xora.org.uk \
--cc=openembedded-devel@lists.openembedded.org \
--cc=paulepanter@users.sourceforge.net \
/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.