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

[Labiaga, Ricardo]

> 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.

I suspect an example would clear this up...  

> But, OK, given the troubles merges seem to be causing, 
> Benny's probably
> right.

The only real troubles I've experienced was moving off 2.6.18 because so
much change happened over the year no changes were merged.  It's been
fairly straight forward keeping it up to date once the we moved it to
2.6.23.  This is a one-time tax for each module if we keep it current.

Thanks for the clarification,

- ricardo