From: Boaz Harrosh <bharrosh@panasas.com>
To: Fred Isaman <iisaman@umich.edu>
Cc: Fred Isaman <iisaman@netapp.com>, linux-nfs@vger.kernel.org
Subject: Re: [PATCH 0/7] LAYOUTGET invocation cleanup patches
Date: Fri, 11 Jun 2010 11:58:57 +0300 [thread overview]
Message-ID: <4C11FAD1.10207@panasas.com> (raw)
In-Reply-To: <AANLkTinwz5TNku2DCC1wszhBngklvOMTJhP7Oho_INJP@mail.gmail.com>
On 06/11/2010 11:47 AM, Fred Isaman wrote:
> On Fri, Jun 11, 2010 at 4:07 AM, Boaz Harrosh <bharrosh@panasas.com> wrote:
>> On 06/11/2010 10:40 AM, Fred Isaman wrote:
>>> These patches, applied to the head of pnfs-all-latest after rebase, bring
>>> the blocklayout back in synch with the generic code changed by my previous
>>> patches and the rebase. The final tree containing the fully rebased tree
>>> with these patches applied is at
>>> git://linux-nfs.org/~isaman/pnfs-block.git in the branch for-benny-20100611.
>>>
>>
>> Grate Fred with a git tree it is actually usable.
>>
>> I will clone your tree. And'll inspect it carefully on the flight.
>> I want to do even more. I'd like to rebase them over an Alexandros-less
>> patchset and actually test them. How hard will that be? Perhaps you
>> might have a branch based on 2.6.34 without Alexandros patches that
>> are up to date? Could you push it for me?
>>
>
> I switched the order of the two patchsets at one point, and it wasn't too hard.
> The original patchset I submitted was based directly on the then
> pnfs-submit tree.
>
> Right now something is wrong with my connection between here and linux-nfs.org.
> At the current rate, the push of the tree I mentioned above will be
> done in about 10 hours :(
>
> I don't think I'll be pushing any other tree soon.
>
> Fred
>
>>> Fred
>>>
Fred I get:
$ git ls-remote git://linux-nfs.org/~isaman/pnfs-block.git
fatal: The remote end hung up unexpectedly
Maybe it's that you are pushing, or there might be a problem.
Perhaps check the permission, or maybe it needs added to git-daemon
(and service restart)
Benny's tree access is fine.
I'll try to connect from home on Saturday and clone it. See if you
can fix the access problem when you are done.
BTW: it should not take so long. You should first clone a tree from
Benny, locally. Do you have a ssh access? then pusshing just your
changes should be very fast. Perhaps you are pushing the full
tree by dialup, that's not smart.
Boaz
next prev parent reply other threads:[~2010-06-11 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 7:40 [PATCH 0/7] LAYOUTGET invocation cleanup patches Fred Isaman
2010-06-11 7:40 ` [PATCH 1/7] SQUASHME: pnfs: export get_lseg and put_lseg Fred Isaman
2010-06-11 7:40 ` [PATCH 2/7] SQUASHME: pnfsblock: write_begin adjust for removed fields Fred Isaman
2010-06-11 7:40 ` [PATCH 3/7] SQUASHME: pnfsblock: write_end adjust for removed ok_to_use_pnfs Fred Isaman
2010-06-11 7:40 ` [PATCH 4/7] SQUASHME: pnfsblock: write_end_cleanup " Fred Isaman
2010-06-11 7:40 ` [PATCH 5/7] SQUASHME: pnfsblock: bl_write_pagelist support functions adjust for missing PG_USE_PNFS Fred Isaman
2010-06-11 7:40 ` [PATCH 6/7] SQUASHME: pnfsblock: bl_write_pagelist " Fred Isaman
2010-06-11 7:40 ` [PATCH 7/7] pnfs: Revert "pnfs_post_submit: Restore "pnfs: pnfs_do_flush" part 2" Fred Isaman
2010-06-11 8:07 ` [PATCH 0/7] LAYOUTGET invocation cleanup patches Boaz Harrosh
2010-06-11 8:47 ` Fred Isaman
2010-06-11 8:58 ` Boaz Harrosh [this message]
2010-06-11 13:44 ` Fred Isaman
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=4C11FAD1.10207@panasas.com \
--to=bharrosh@panasas.com \
--cc=iisaman@netapp.com \
--cc=iisaman@umich.edu \
--cc=linux-nfs@vger.kernel.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