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

[Benny Halevy]

J. Bruce Fields wrote:
> On Mon, Dec 03, 2007 at 07:21:42PM -0800, Ricardo Labiaga wrote:
>   
>> So you're proposing to take the same content of linux-pnfs-2.6-latest
>> and basically generate a set of patches to keeps moving forward?
>>
>> I don't yet understand git well enough, but I've heard that git-rebase
>> is the wrong thing to use when you're sharing the repository with
>> others.  As I understood it, every rebase loses your history and messes
>> up those who have cloned from you.  Did I misunderstand?
>>     
>
> 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.
>
> Also unless you take extra steps to save old versions of the patch
> series you may have trouble, e.g., identifying regressions from one to
> the next.
>   
Right.  What I thought of is creating a branch before the rebase to 
provide a frozen snapshot
at this point.