[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140509072603.GH26890@mwanda>
Date: Fri, 9 May 2014 10:26:03 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Namhyung Kim <namhyung@...nel.org>
Cc: devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org,
linux-doc@...r.kernel.org
Subject: Re: [patch v2] Documentation/email-clients.txt: add a section about
git
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
--
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/
Powered by blists - more mailing lists