All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	"Xen-devel@lists.xensource.com" <Xen-devel@li>
Subject: Re: Re: [PATCH] Remus breaks the build
Date: Wed, 18 Aug 2010 16:54:02 -0700	[thread overview]
Message-ID: <4C6C729A.7030206@goop.org> (raw)
In-Reply-To: <20100818202650.GD2411@kremvax.cs.ubc.ca>

 On 08/18/2010 01:26 PM, Brendan Cully wrote:
> That's more git than I've learned. Would a patch suffice? (even
> producing the diff was non-obvious. It turns out that git add foo; git
> diff doesn't include the diff for foo!)

What's the origin of the code?  Do they have a git tree (I seem to
remember one).  I can pull from that, then apply any local patches you
may have.

    J

  parent reply	other threads:[~2010-08-18 23:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13  0:38 [PATCH] Remus breaks the build Jeremy Fitzhardinge
2010-08-13 10:38 ` Ian Campbell
2010-08-13 11:55   ` Stefano Stabellini
2010-08-13 12:52     ` Ian Jackson
2010-08-13 19:44       ` Brendan Cully
2010-08-18 20:09         ` Brendan Cully
2010-08-13 19:42 ` Brendan Cully
2010-08-13 21:14   ` Jeremy Fitzhardinge
2010-08-14  4:25     ` Dulloor
2010-08-17 17:38       ` Brendan Cully
2010-08-18 13:40         ` Ian Jackson
2010-08-18 17:58           ` Brendan Cully
2010-08-19 14:38             ` Ian Jackson
2010-08-18 20:26     ` Brendan Cully
2010-08-18 20:34       ` Jed Smith
2010-08-18 20:39         ` Brendan Cully
2010-08-18 23:54       ` Jeremy Fitzhardinge [this message]
2010-08-19  0:03         ` Brendan Cully
2010-08-19  6:03           ` Pasi Kärkkäinen

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=4C6C729A.7030206@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Xen-devel@li \
    --cc=stefano.stabellini@eu.citrix.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.