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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20090427.181419.47244869.davem@davemloft.net>
Date:	Mon, 27 Apr 2009 18:14:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	karsten-keil@...nline.de
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH v2 0/3] [ISDN] Documentation patchset

From: Karsten Keil <karsten-keil@...nline.de>
Date: Mon, 27 Apr 2009 15:13:32 +0200

> 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 ?

Yes, it's perfectly fine to put the author's From: field in
the body.  And as the patch submitter your should preserve
your From: in the normal email headers.  That's how it's
supposed to be :-)
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ