From: Michael Ellerman <michael@ellerman.id.au>
To: Joe Perches <joe@perches.com>
Cc: Rob Landley <rob@landley.net>, Matt Mackall <mpm@selenic.com>,
Robin Getz <rgetz@blackfin.uclinux.org>,
Sam Ravnborg <sam@ravnborg.org>,
Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>,
Denis Vlasenko <vda.linux@googlemail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] update kernel's scripts/bloat-o-meter from busybox
Date: Tue, 02 Jun 2009 16:33:39 +1000 [thread overview]
Message-ID: <1243924419.6119.3.camel@concordia> (raw)
In-Reply-To: <1243923058.3402.66.camel@Joe-Laptop.home>
[-- Attachment #1: Type: text/plain, Size: 540 bytes --]
On Mon, 2009-06-01 at 23:10 -0700, Joe Perches wrote:
> On Tue, 2009-06-02 at 00:59 -0500, Rob Landley wrote:
> > P.S. I'd attach the 5 patch+descriptions, but I just spent fifteen minutes
> > fighting with git to try to convince "git log -p" that when I list a specific
> > commit on the command line I want it to spit out the description and patch for
> > JUST THAT ONE COMMIT and not log the history back to Grace Hopper's graduation
> > ceremony
>
> git log -p -1 commit
Or more simply:
git show <commit>
cheers
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2009-06-02 6:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-01 19:26 [PATCH] update kernel's scripts/bloat-o-meter from busybox Robin Getz
2009-06-01 19:48 ` Matt Mackall
2009-06-01 20:39 ` Mike Frysinger
2009-06-01 20:57 ` Robin Getz
2009-06-01 21:17 ` Matt Mackall
2009-06-02 6:04 ` Rob Landley
2009-06-02 13:07 ` Bernhard Reutner-Fischer
2009-06-02 20:11 ` Robin Getz
2009-06-05 21:42 ` Sam Ravnborg
2009-06-10 12:27 ` Denys Vlasenko
2009-06-14 20:37 ` Sam Ravnborg
2009-06-02 5:59 ` Rob Landley
2009-06-02 6:10 ` Joe Perches
2009-06-02 6:33 ` Michael Ellerman [this message]
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=1243924419.6119.3.camel@concordia \
--to=michael@ellerman.id.au \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=rep.dot.nop@gmail.com \
--cc=rgetz@blackfin.uclinux.org \
--cc=rob@landley.net \
--cc=sam@ravnborg.org \
--cc=vda.linux@googlemail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.