From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Patches for 2.6.33-rc1
Date: Wed, 9 Dec 2009 12:49:33 +0000 [thread overview]
Message-ID: <20091209124933.GE9018@sirena.org.uk> (raw)
In-Reply-To: <1260355174.13499.8.camel@pc1117.cambridge.arm.com>
On Wed, Dec 09, 2009 at 10:39:34AM +0000, Catalin Marinas wrote:
> It would be useful, indeed, so I haven't seen an official statement from
> Russell on this (and I usually run gitk on specific directories).
I'd suggest using ARM: like the patch system does. In general looking
at the logs for the directory/file you're updating and using the same
prefix as most of the commits works well.
next prev parent reply other threads:[~2009-12-09 12:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-09 10:09 [GIT PULL] Patches for 2.6.33-rc1 Catalin Marinas
2009-12-09 10:20 ` Artem Bityutskiy
2009-12-09 10:39 ` Catalin Marinas
2009-12-09 11:04 ` Artem Bityutskiy
2009-12-09 11:23 ` Artem Bityutskiy
2009-12-09 12:43 ` Catalin Marinas
2009-12-09 12:49 ` Mark Brown [this message]
2009-12-09 13:21 ` Catalin Marinas
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=20091209124933.GE9018@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--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).