git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Folkert van Heusden <folkert@vanheusden.com>
To: git@vger.kernel.org
Subject: retrieving a diff from git
Date: Tue, 14 Oct 2008 16:51:12 +0200	[thread overview]
Message-ID: <20081014145112.GR22427@vanheusden.com> (raw)

Hi,

How would I retrieve the 'kmemcheck' patches from git for the 2.6.27
kernel? I browsed to the url
http://git.kernel.org/?p=linux%2Fkernel%2Fgit%2Fx86%2Flinux-2.6-tip.git&a=search&h=HEAD&st=commit&s=kmemcheck
but could not find how to retrieve that diff.


Folkert van Heusden

-- 
Ever wonder what is out there? Any alien races? Then please support
the seti@home project: setiathome.ssl.berkeley.edu
----------------------------------------------------------------------
Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com

             reply	other threads:[~2008-10-14 15:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-14 14:51 Folkert van Heusden [this message]
2008-10-14 17:01 ` retrieving a diff from git Alex Riesen
2008-10-14 17:20   ` Folkert van Heusden
2008-10-14 17:29     ` Alex Riesen
2008-10-14 17:56     ` Matthieu Moy
2008-10-15 10:12     ` Christian Jaeger

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=20081014145112.GR22427@vanheusden.com \
    --to=folkert@vanheusden.com \
    --cc=git@vger.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;
as well as URLs for NNTP newsgroup(s).