linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Nick Piggin <npiggin@suse.de>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	open-osd <osd-dev@open-osd.org>
Subject: Re: [RFC] exofs: New truncate sequence
Date: Tue, 01 Jun 2010 14:05:35 +0300	[thread overview]
Message-ID: <4C04E97F.8060001@panasas.com> (raw)
In-Reply-To: <20100601104454.GB2057@lst.de>

On 06/01/2010 01:44 PM, Christoph Hellwig wrote:
> On Tue, Jun 01, 2010 at 01:26:30PM +0300, Boaz Harrosh wrote:
>> Imagine my surprise when this morning I see that all of Al's patches
>> are in mainline. (that was sarcastic, Stupid me they where there yesterday)
>>
>> So I'm posting a final version of this patch. It runs over 2.6.35-rc1
>> and works really well and I like this patch a lot. I'm putting it
>> in osd/linux-next.
>>
>> Please advise: Should I ask Linus to pull this in for current Kernel?
>> If not, then I'll ask Al to put it in his tree for 2.6.36 and you can
>> rebase over his tree.
> 
> With the other changes I have you'll be much better off rebasing
> ontop of my series as it will make your life easier.  But if you're
> eager to push it out please do it ASAP.
> 

I would prefer to push it, because it will be much easier for me
when juggling with the pnfs tree, Which is based on 2.6.35-rc1.

Thanks
Boaz

  reply	other threads:[~2010-06-01 11:05 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-31 12:30 [RFC] exofs: New truncate sequence Boaz Harrosh
2010-05-31 13:44 ` Nick Piggin
2010-05-31 14:13   ` Boaz Harrosh
2010-05-31 14:33     ` Nick Piggin
2010-05-31 14:50       ` Boaz Harrosh
2010-05-31 15:09         ` Nick Piggin
2010-05-31 15:19           ` Boaz Harrosh
2010-06-01 10:08             ` Christoph Hellwig
2010-06-01 10:26               ` Boaz Harrosh
2010-06-01 10:44                 ` Christoph Hellwig
2010-06-01 11:05                   ` Boaz Harrosh [this message]
2010-06-01 11:06                     ` Christoph Hellwig
2010-06-01 10:28 ` [PATCH ver2] " Boaz Harrosh
2010-06-01 10:43   ` Christoph Hellwig
2010-06-01 10:59     ` Boaz Harrosh
2010-06-01 11:06       ` Christoph Hellwig
2010-06-01 11:31 ` [PATCH ver3] " Boaz Harrosh
2010-06-01 11:36   ` Christoph Hellwig
2010-06-01 11:52     ` Boaz Harrosh
2010-06-01 15:09   ` Nick Piggin

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=4C04E97F.8060001@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=hch@lst.de \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=npiggin@suse.de \
    --cc=osd-dev@open-osd.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).