[pnfs] A git-tree with my last 19 linux-pnfs-2.6-latest READI/O patches

[Benny Halevy]

Labiaga, Ricardo wrote:
>> Well, it's a tradeoff.  You're essentially restarting the history from
>> scratch each time.  That means for example if someone else is building
>> work on top of your work, then they have to manually figure out where
>> their series ended and your patches began in order to port 
>> them forward
>> to a new version of your branch.
>>     
>
> What I'm hearing from Benny leads me to think that every patch gets
> rebased multiple times until we're ready to push upstream.  So basically
> any new work needs to be manually figured out from now till we push it?
> That would be months of manual work by all of us over and over.  I'm
> probably missing something.
>   
That's right but:
a. the porting work is done in any case. it just finds its way to the 
merge commits rather than the patches.
b. doing that in small increments shouldn't take a lot of effort and it 
really helps you with understanding
what's coming up the stream and your dependencies on it.
> I suspect an example would clear this up...  
>