From: Dan Carpenter <dan.carpenter@oracle.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [patch v2] Documentation/email-clients.txt: add a section about git
Date: Fri, 9 May 2014 10:26:03 +0300 [thread overview]
Message-ID: <20140509072603.GH26890@mwanda> (raw)
In-Reply-To: <8738gjol2f.fsf@sejong.aot.lge.com>
On Fri, May 09, 2014 at 09:24:56AM +0900, Namhyung Kim wrote:
> > +Git
> > +----------------------------------------------------------------------
> > +These days most developers use `git send-email` instead of regular
> > +email clients. 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 `cat raw_email.txt | git am`
> > +and then review the changelog with `git log -p`. When that works then
>
> Also the -p option is not needed for just checking the changelog IMHO.
> If one needs to check the patch itself too, I think `git show` is
> slightly better since it only shows the single commit applied.
>
I know you can leave the -p off but I wanted it on and I wanted the log
so they could see their patch and how the format compared to other
commits.
You guys are over thinking this. It's not commands for all ages. If
you type `cat patch.txt | git am` or if you type `git am < patch.txt`,
those are things I don't care about.
regards,
dan carpenter
next prev parent reply other threads:[~2014-05-09 7:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 11:17 [patch] Documentation/email-clients.txt: add a section about git Dan Carpenter
2014-05-07 16:06 ` Laura Abbott
2014-05-07 16:18 ` Dan Carpenter
2014-05-08 8:44 ` [patch v2] " Dan Carpenter
2014-05-08 9:05 ` Julian Andres Klode
2014-05-08 9:28 ` Hillf Danton
2014-05-09 7:28 ` Dan Carpenter
2014-05-09 0:24 ` Namhyung Kim
2014-05-09 7:26 ` Dan Carpenter [this message]
2014-05-11 0:19 ` Randy Dunlap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140509072603.GH26890@mwanda \
--to=dan.carpenter@oracle.com \
--cc=devel@driverdev.osuosl.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox