linux-kernel - Re: [PATCH v2] Add support for usbfs zerocopy.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <878u31phih.fsf@ti.com>
Date:	Thu, 04 Feb 2016 00:15:50 +0200
From:	Felipe Balbi <balbi@...nel.org>
To:	"Steinar H. Gunderson" <sesse@...gle.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org,
	stern@...land.harvard.edu
Subject: Re: [PATCH v2] Add support for usbfs zerocopy.

"Steinar H. Gunderson" <sesse@...gle.com> writes:

> On Wed, Feb 03, 2016 at 01:23:17PM -0800, Greg Kroah-Hartman wrote:
>> Attachments don't work, you know better than that :(
>
> Since I've now been bitten by this several times: Is there any sort of best
> practice for integrating git with MUAs? What I'm doing right now is
> cut-and-paste from mutt to get the to/cc/in-reply-to headers right, and
> that's suboptimal. It feels like it should be a FAQ, but I can't really find
> anything obvious.

have you tried git send-email ? If you wanna send as a reply to another
message, use:

  $ git send-email --to foo@....com --cc bar@....com --in-reply-to=abcd-message-id@....bar.com

note that git send-email can read mutt aliases. It's all documented in
the man page:

  $ git help send-email

-- 
balbi

Download attachment "signature.asc" of type "application/pgp-signature" (819 bytes)