On Friday 14 October 2011 13:42:07 Simon Glass wrote:
On Fri, Oct 14, 2011 at 10:09 AM, Mike Frysinger wrote:
On Friday 14 October 2011 12:47:56 Simon Glass wrote:
On Thu, Oct 13, 2011 at 6:53 PM, Mike Frysinger wrote:
subject is "int" but implementation is "ulong"
Yes - I wonder if I can just submit a V2 for that one patch with a new subject?
that's fine (i do it all the time). although in the future, your v2 should probably have the reply-to field set to the v1 patch.
OK I need to figure out how to do that with git send-email. I can see how to do it with a single email, but I suppose if I post a V2 then every email should be in reply to its corresponding V1, is that right?
if you send out a whole new patchseries, i don't think each sub patch should be a reply to the original. having it be a new tree by itself is fine.
BTW I also need some patchwork automation since a lot of the patches marked 'NEW' in there are not - 'pwclient update' is most of it I suppose, if it had an option to get my password back - no reply to this:
http://lists.ozlabs.org/pipermail/patchwork/2010-December/000347.html
i've only used the web interface so far. and this extension makes life a lot easier when you have to select a lot (but not all) of the patches in a query: https://chrome.google.com/webstore/detail/ldopaogbegnhconlboidfjcmidndkbeg -mike