Re: [git patches] 2.6.x libata updates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




On Sun, 30 Oct 2005, Rob Landley wrote:
> 
> Rather than making the patch a simple diff of the trees, make the patch a cat 
> of the individual patches/commits (preferably with descriptions) that got 
> applied, in the order they got applied.
> 
> This makes the patch bigger, but it also means that bisect can be done with 
> vi, simply by truncating the file at the last interesting patch and applying 
> the truncated version to a clean tree.  Since patch applies hunks in order 
> and sifts out hunks from description already...
> 
> Is this a viable option?

No.

There is no "ordering" in a distributed environment. We have things 
happening in parallel, adn you can't really linearize the patches.

The closest you can get is "git bisect", which does the right thing.

		Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux