linux-kernel - Re: [patch v2] Documentation/email-clients.txt: add a section about git

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: <CAJd=RBBNbJnTsu=73o9Yy4dgVw2zUJR9Cc5=eZB+U+WqJ=4KDg@mail.gmail.com>
Date:	Thu, 8 May 2014 17:28:46 +0800
From:	Hillf Danton <dhillf@...il.com>
To:	Julian Andres Klode <jak@...-linux.org>,
	Dan Carpenter <dan.carpenter@...cle.com>,
	Randy Dunlap <rdunlap@...radead.org>,
	devel@...verdev.osuosl.org, LKML <linux-kernel@...r.kernel.org>,
	linux-doc@...r.kernel.org
Subject: Re: [patch v2] Documentation/email-clients.txt: add a section about git

On Thu, May 8, 2014 at 5:05 PM, Julian Andres Klode <jak@...-linux.org> wrote:
> On Thu, May 08, 2014 at 11:44:12AM +0300, Dan Carpenter wrote:
>> +as raw text including all the headers.  Run `cat raw_email.txt | git am`
>
> `cat raw_email.txt | git am` seems a bit pointless. Why not simply
> `git am raw_email.txt`? `git am < raw_email.txt` does the same too
> and avoids the useless cat as well.
>
> No point in running two processes when the same can be done in a
> simpler way in one process, IMO.
>
And this helps most developers little, but is more valuable for those who
dont use 'git send-mail' everyday if the detail of cmdline is provided, say
send a patch file with 'git send-mail' through gmail.

We will say double thanks to you, Dan, if you really help us tame gmail.

And a howto to tame gmail is doule apprecaited.

thanks
Hillf
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/