From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Serafini Date: Thu, 6 Nov 2014 16:33:16 +0100 Subject: [Buildroot] [PATCH v2] exiv2: new package In-Reply-To: <545B8FC9.30305@imgtec.com> References: <1415285886-11117-1-git-send-email-nicolas.serafini@sensefly.com> <545B8ECE.9000208@sensefly.com> <545B8FC9.30305@imgtec.com> Message-ID: <545B94BC.1080800@sensefly.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net 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, >