All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Haigh <netwiz-tY1ak9Q0PTWHXe+LvDLADg@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Creating a patch against upstream kernel 3.7.4
Date: Wed, 23 Jan 2013 12:36:41 +1100	[thread overview]
Message-ID: <50FF3EA9.1020109@crc.id.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

Hi all,

I'm quite a n00b when it comes to the ins and outs of using git... My 
last real project using something like this was when CVS was all the rage!

I'm wanting to try to make an automated method to create a single patch 
file for all the changes required against the upstream kernel version. 
This will allow me to easily manage changes until things are merged. It 
will also allow a one-liner in my Xen Dom0 scripting to let me patch 
bcache into the kernel (good!).

Does git have a way to do this?

I just tried to check out the bcache tree, but I just got:
$ git clone http://evilpiepirate.org/git/linux-bcache.git
Initialized empty Git repository in /home/netwiz/linux-bcache/.git/
error: RPC failed; result=22, HTTP code = 405

and nothing more.

-- 
Steven Haigh

Email: netwiz-tY1ak9Q0PTWHXe+LvDLADg@public.gmane.org
Web: http://www.crc.id.au
Phone: (03) 9001 6090 - 0412 935 897
Fax: (03) 8338 0299


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4965 bytes --]

             reply	other threads:[~2013-01-23  1:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-23  1:36 Steven Haigh [this message]
     [not found] ` <50FF3EA9.1020109-tY1ak9Q0PTWHXe+LvDLADg@public.gmane.org>
2013-01-24 23:41   ` Creating a patch against upstream kernel 3.7.4 Kent Overstreet

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=50FF3EA9.1020109@crc.id.au \
    --to=netwiz-ty1ak9q0ptwhxe+lvdladg@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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.