From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: Link failures due to __bug_table in current -next
Date: Tue, 20 Sep 2011 09:35:04 +0200 [thread overview]
Message-ID: <20110920073504.GI23628@pengutronix.de> (raw)
In-Reply-To: <20110919191617.GB16381@n2100.arm.linux.org.uk>
On Mon, Sep 19, 2011 at 08:16:17PM +0100, Russell King - ARM Linux wrote:
> On Mon, Sep 19, 2011 at 08:06:03PM +0100, Mark Brown wrote:
> > Yeah, it's a shame it doesn't include the disambiguated short ID in the
> > standard git log output (which is what I always grep if I'm trying to
> > search commit messages). I've never seen a way to tell git to use %H
> > instead of %h there by default that doesn't require me to start copying
> > scripts or whatever between machines all the time.
>
> I'm in two minds over this:
>
> [format]
> pretty = %h %s
>
> which I currently have in my ~/.gitconfig file. It means that I always
> get git log output as:
>
> 38c0a0c Merge branches 'apei', 'bz-13195' and 'doc' into acpi
> b6fd41e Linux 3.1-rc6
> 8cb3ed17 Merge branch 'drm-fixes' of git://people.freedesktop.org/~airlied/linux4c75278 Merge branch 'fixes' of git://git.linaro.org/people/arnd/arm-soc
> 14d01ff ioctl: register LTTng ioctl
>
> rather than the more usual medium-pretty output. I can get that by
> using git log --pretty=medium. The alternative to that is to use
> shell aliases to pass the --pretty= argument for a gitslog alias -
> or I believe you can create git command aliases in the ~/.gitconfig file.
> (Never tried it yet, something I need to look at.)
I did:
git config --global alias.lg "log --pretty=oneline --abbrev-commit"
git config --global alias.one "show -s --pretty='format:%h (%s)"
which results in
[alias]
lg = log --pretty=oneline --abbrev-commit
one = show -s --pretty='format:%h (%s)'
and makes available the commands
git lg
(for summary logging) and
git one
(to format a commit id for use in another commit message).
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-09-20 7:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-19 12:09 Link failures due to __bug_table in current -next Mark Brown
2011-09-19 18:40 ` Russell King - ARM Linux
2011-09-19 18:42 ` Mark Brown
2011-09-19 18:58 ` Russell King - ARM Linux
2011-09-19 19:06 ` Mark Brown
2011-09-19 19:16 ` Russell King - ARM Linux
2011-09-20 7:35 ` Uwe Kleine-König [this message]
2011-09-19 19:12 ` Russell King - ARM Linux
2011-09-19 20:03 ` Russell King - ARM Linux
2011-09-20 7:06 ` Simon Glass
2011-09-20 7:59 ` Russell King - ARM Linux
2011-09-20 17:00 ` Simon Glass
2011-09-20 18:51 ` Russell King - ARM Linux
2011-09-20 19:13 ` Arnd Bergmann
2011-09-20 19:57 ` Nicolas Pitre
2011-09-21 22:58 ` Simon Glass
2011-09-21 22:45 ` Simon Glass
2011-09-20 11:02 ` Mark Brown
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=20110920073504.GI23628@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).