mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Fasheh <mfasheh@suse.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
	Joel Becker <joel.becker@oracle.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [git patches] Ocfs2 updates for 2.6.30
Date: Fri, 3 Apr 2009 13:34:12 -0700	[thread overview]
Message-ID: <20090403203412.GD14571@wotan.suse.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0904031214260.4015@localhost.localdomain>

On Fri, Apr 03, 2009 at 12:17:35PM -0700, Linus Torvalds wrote:
> > Are they likely? Probably not. But that's not the point. The point is that 
> > you barely had time to compile that thing, much less give it any testing.
> 
> Gaah. I pulled it anyway. Today, I just can't find it in me to care about 
> ocfs2 testing.

Heh, thanks I guess :)


> But please - keep this in mind. Even if the commit is old, when you rebase 
> it, you really do move it into a whole new world order. And yes, it 
> _usually_ works just fine. 
> 
> But to make sure, please do spend some time after setting up the tree to 
> make sure that what I get really is something that you know is what I want 
> to get.

Point taken. Actually, the pre-rebased branch would have merged fine too, so
I really just rebased because of old habit, which isn't a good reason,
obviously.

Next time, I'll rebase early enough so that we can get a reasonable amount
of testing in.
	--Mark

--
Mark Fasheh

  reply	other threads:[~2009-04-03 20:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 18:46 Mark Fasheh
2009-04-03 19:13 ` Linus Torvalds
2009-04-03 19:17   ` Linus Torvalds
2009-04-03 20:34     ` Mark Fasheh [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-17 20:00 Mark Fasheh

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=20090403203412.GD14571@wotan.suse.de \
    --to=mfasheh@suse.com \
    --cc=akpm@linux-foundation.org \
    --cc=joel.becker@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ocfs2-devel@oss.oracle.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®