From: Petri Lehtinen <petri.lehtinen+openembedded-devel@inoi.fi>
To: openembedded-devel@lists.openembedded.org
Cc: Petri Lehtinen <petri.lehtinen@inoi.fi>
Subject: Re: [PATCH] python-flup: Bump to version 1.0.2
Date: Tue, 29 Sep 2009 10:57:44 +0300 [thread overview]
Message-ID: <20090929075744.GG12219@colossus> (raw)
In-Reply-To: <200909290932.41751.holger+oe@freyther.de>
Holger Hans Peter Freyther wrote:
> On Tuesday 29 September 2009 09:19:13 Petri Lehtinen wrote:
> > From: Petri Lehtinen <petri.lehtinen@inoi.fi>
> >
> >
> > Signed-off-by: Petri Lehtinen <petri.lehtinen@inoi.fi>
>
> Signed-off-by: Holger Hans Peter Freyther <zecke@selfish.org>
>
>
> in the future please use the -BMC option to detect renames properly.
OK.
--
Petri Lehtinen
Software Specialist
Inoi Oy
Tel. : +358 40 758 0229
Email: petri.lehtinen@inoi.fi
prev parent reply other threads:[~2009-09-29 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-29 7:19 [PATCH] python-flup: Bump to version 1.0.2 Petri Lehtinen
2009-09-29 7:32 ` Holger Hans Peter Freyther
2009-09-29 7:57 ` Petri Lehtinen [this message]
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=20090929075744.GG12219@colossus \
--to=petri.lehtinen+openembedded-devel@inoi.fi \
--cc=openembedded-devel@lists.openembedded.org \
--cc=petri.lehtinen@inoi.fi \
/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