From: Suresh Jayaraman <sjayaraman-l3A5Bk7waGM@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Shirish Pargaonkar
<shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: 2.6.36 merge plans
Date: Tue, 03 Aug 2010 10:25:06 +0530 [thread overview]
Message-ID: <4C57A12A.1030404@suse.de> (raw)
In-Reply-To: <AANLkTim-fb4obi7KBxpUsyeYi4eAQmTuSAx+14jOE3kr-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 08/03/2010 03:44 AM, Steve French wrote:
> On Mon, Aug 2, 2010 at 12:46 PM, Jeff Layton <jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org> wrote:
>> On Fri, 23 Jul 2010 17:19:29 -0500
>> Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> I had no problem with the last patch in your tree, but wanted
> to test the one before it (the creation time patch) before merging,
> and thought it would be easier to merge them in order since
> they hit at least one file in common.
>
> Backing out the one patch I wanted to test more with Samba (the
> creation time one)
> I made a big merge request today to clear the 27 patches queued up already,
> and expect to merge your last two and Dave's DNS one and probably
> Shirish's (if they can be tested/reviewed more) this week.
>
Steve, are you considering the following patches as well..?
cifs: show features compiled in as part of DebugData
cifs: update README
(I think there are no outstanding issues left unaddressed).
Thanks,
--
Suresh Jayaraman
next prev parent reply other threads:[~2010-08-03 4:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTim2UcxAXuR0K8JexGAIq3UoEj1KMH4JMGLnJ72D@mail.gmail.com>
[not found] ` <20100630141755.4ac97143@tlielax.poochiereds.net>
[not found] ` <4C2CDD02.2090403@suse.de>
[not found] ` <AANLkTilEg0zG1DD9fF9T890nFhaqNNeLta1-RAo9iKpM@mail.gmail.com>
[not found] ` <AANLkTimTjDJeR7ktNcJpPSc-zioHrndPwPxb98HAYgpY@mail.gmail.com>
[not found] ` <20100701195247.71c3f572@tlielax.poochiereds.net>
[not found] ` <20100701195247.71c3f572-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-07-23 22:19 ` 2.6.36 merge plans Steve French
[not found] ` <AANLkTi=X5PyZLdaJj_ikSv7HUNtfmQYhPc50mecx_mMj-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-07-23 23:13 ` Jeff Layton
2010-08-04 4:31 ` Steve French
[not found] ` <AANLkTi=_BzaDhRhOZa8tGjfyE2hnguuE5HTH-rqJUw8o-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-04 10:49 ` Jeff Layton
2010-08-02 17:46 ` Jeff Layton
[not found] ` <20100802134654.3ac129e7-9yPaYZwiELC+kQycOl6kW4xkIHaj4LzF@public.gmane.org>
2010-08-02 22:14 ` Steve French
[not found] ` <AANLkTim-fb4obi7KBxpUsyeYi4eAQmTuSAx+14jOE3kr-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-08-03 4:55 ` Suresh Jayaraman [this message]
[not found] ` <4C57A12A.1030404-l3A5Bk7waGM@public.gmane.org>
2010-08-03 14:02 ` Steve French
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=4C57A12A.1030404@suse.de \
--to=sjayaraman-l3a5bk7wagm@public.gmane.org \
--cc=jlayton-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=shirishpargaonkar-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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