public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Zach Brown <zach.brown@oracle.com>, Andrew Morton <akpm@osdl.org>,
	Joel Becker <Joel.Becker@oracle.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Christoph Hellwig <hch@lst.de>,
	Wim Coekaerts <wim.coekaerts@oracle.com>,
	Mark Fasheh <mark.fasheh@oracle.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: merging ocfs2?
Date: Thu, 5 Jan 2006 15:37:15 +0100	[thread overview]
Message-ID: <20060105143715.GA24927@lst.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0601041649270.3668@g5.osdl.org>

On Wed, Jan 04, 2006 at 04:50:49PM -0800, Linus Torvalds wrote:
> 
> 
> On Tue, 3 Jan 2006, Zach Brown wrote:
> >
> > Joel has done the heavy lifting to bring its git repository up to date
> > so one should be able to pull from:
> > 
> >   http://oss.oracle.com/git/ocfs2.git
> 
> If Christoph is happy with it, and there has been no grumbling from -mm, I 
> can certainly merge it.

Last time I looked it seemed fine.  That's been about a month ago and
I don't have time to look over it again currently.  I'd say merge it and
blame everything on me if something horrible is hidden inside now :)


  parent reply	other threads:[~2006-01-05 14:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-03 22:22 merging ocfs2? Zach Brown
2006-01-04  3:17 ` Andrew Morton
2006-01-05  0:50 ` Linus Torvalds
2006-01-05  1:09   ` Zach Brown
2006-01-05  1:11     ` Wim Coekaerts
2006-01-05  1:22   ` Joel Becker
2006-01-05 14:37   ` Christoph Hellwig [this message]
2006-01-06  4:38   ` Wim Coekaerts

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=20060105143715.GA24927@lst.de \
    --to=hch@lst.de \
    --cc=Joel.Becker@oracle.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.fasheh@oracle.com \
    --cc=torvalds@osdl.org \
    --cc=wim.coekaerts@oracle.com \
    --cc=zach.brown@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox