| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 27 Apr 2009 15:13:32 +0200 From: Karsten Keil <karsten-keil@...nline.de> To: David Miller <davem@...emloft.net> Cc: netdev@...r.kernel.org Subject: Re: [PATCH v2 0/3] [ISDN] Documentation patchset On Monday, 27. April 2009 14:39:02 you wrote: ... > > Here they are in patchwork, they don't apply: > > http://patchwork.ozlabs.org/patch/26362/ > http://patchwork.ozlabs.org/patch/26363/ > http://patchwork.ozlabs.org/patch/26361/ > > Oh I see what happened. > > IT'S THOSE STUPID "Date:" fields you added to the body of 2 of those > patches. It caused patchwork to put them in the wrong order when I > put them together into a bundle. > > Don't add extra email header fields like that, please! :-) > > I fixed it up and applied the patches. Thanks, sorry for the extra work. I did add the headers (Date and From) to preserve the ownership and original date, with plain git it works very well. I can leave out the date field, but if I resend patch from a other developer (which I signed or acked as maintainer), I need to move the original From into the body, my uplink rewrites the From with my address. Would this be still OK or does the From in the body make also problems with patchwork ? Other way would be to setup a cloned net-2.6 isdn tree, so you can pull patches directly. Karsten -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists