From: Jeff Garzik <jeff@garzik.org>
To: Benny Halevy <bhalevy@panasas.com>
Cc: Boaz Harrosh <bharrosh@panasas.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
open-osd mailing-list <osd-dev@open-osd.org>
Subject: Re: [osd-dev] [GIT PULL] exofs/osd tree for 2.6.31
Date: Tue, 07 Jul 2009 09:58:46 -0400 [thread overview]
Message-ID: <4A535496.1070801@garzik.org> (raw)
In-Reply-To: <4A522E57.7060101@panasas.com>
Benny Halevy wrote:
> Sorry for nagging.
> Is this going to be merged in 2.6.31 or wait for 2.6.32?
> Anything we can do to help it not fall between the cracks next time?
I guess Boaz just needs to resubmit the push to Linus?
His reply was probably not as clear as a regenerated pull request.
Jeff
prev parent reply other threads:[~2009-07-07 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 8:50 [GIT PULL] exofs/osd tree for 2.6.31 Boaz Harrosh
2009-06-22 8:50 ` Boaz Harrosh
2009-06-24 9:39 ` [osd-dev] " Boaz Harrosh
2009-06-24 9:39 ` Boaz Harrosh
2009-07-06 17:03 ` Benny Halevy
2009-07-07 13:58 ` Jeff Garzik [this message]
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=4A535496.1070801@garzik.org \
--to=jeff@garzik.org \
--cc=bhalevy@panasas.com \
--cc=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--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 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.