From: Nicolas Serafini <nicolas.serafini@sensefly.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] exiv2: new package
Date: Thu, 6 Nov 2014 16:33:16 +0100 [thread overview]
Message-ID: <545B94BC.1080800@sensefly.com> (raw)
In-Reply-To: <545B8FC9.30305@imgtec.com>
Dear Vicente Olivert Riera,
Thank you for the information I did not know this feature into patchwork
Best regards
Nicolas
Le 06. 11. 14 16:12, Vicente Olivert Riera a ?crit :
> Dear Nicolas Serafini,
>
> On 11/06/2014 03:07 PM, Nicolas Serafini wrote:
>> Hi all,
>>
>> Do not take into account this patch I was a little to fast.
>>
>> v3 is comming
>
> if you have an account in patchwork, you can change the state of your
> own patches. So, when you send a new version of a patch, you can mark
> the old one as superseded, for instance.
>
> Or, if your patch is not ok are you have been asked to do some changes,
> you can set the state to "Changes requested".
>
> If you do that, people will not "waste" their time testing those patches
> because they will know you are going to submit an updated version.
>
> Best regards,
>
prev parent reply other threads:[~2014-11-06 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 14:58 [Buildroot] [PATCH v2] exiv2: new package Nicolas Serafini
2014-11-06 15:07 ` Nicolas Serafini
2014-11-06 15:12 ` Vicente Olivert Riera
2014-11-06 15:33 ` Nicolas Serafini [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=545B94BC.1080800@sensefly.com \
--to=nicolas.serafini@sensefly.com \
--cc=buildroot@busybox.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.