From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755215AbaEOVB6 (ORCPT ); Thu, 15 May 2014 17:01:58 -0400 Received: from merlin.infradead.org ([205.233.59.134]:38124 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751076AbaEOVB4 (ORCPT ); Thu, 15 May 2014 17:01:56 -0400 Message-ID: <53752B41.5070709@infradead.org> Date: Thu, 15 May 2014 14:01:53 -0700 From: Randy Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Dan Carpenter CC: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org Subject: Re: [patch v4] Documentation/email-clients.txt: add a section about git References: <20140515093328.GA31597@mwanda> In-Reply-To: <20140515093328.GA31597@mwanda> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/15/2014 02:33 AM, Dan Carpenter wrote: > These days most people use git to send patches so I have added a section > about that. > > Signed-off-by: Dan Carpenter Applied. Thanks. > --- > v2: fix typo in commit message > v3: update git am and log commands. Mention the man pages. > v4: s/list/appropriate mailing list(s)/ > > diff --git a/Documentation/email-clients.txt b/Documentation/email-clients.txt > index 4e30eba..9293477 100644 > --- a/Documentation/email-clients.txt > +++ b/Documentation/email-clients.txt > @@ -1,6 +1,17 @@ > Email clients info for Linux > ====================================================================== > > +Git > +---------------------------------------------------------------------- > +These days most developers use `git send-email` instead of regular > +email clients. The man page for this is quite good. On the receiving > +end, maintainers use `git am` to apply the patches. > + > +If you are new to git then send your first patch to yourself. Save it > +as raw text including all the headers. Run `git am raw_email.txt` and > +then review the changelog with `git log`. When that works then send > +the patch to the appropriate mailing list(s). > + > General Preferences > ---------------------------------------------------------------------- > Patches for the Linux kernel are submitted via email, preferably as > _______________________________________________ -- ~Randy