> > > > The problem I find is that I often want to take (file1+patch) -> file2,
> > > > when I don't have file1. But merge tools want to take (file1|file2) -> file3.
> > > > I haven't seen a graphical tool which helps you to wiggle a patch into
> > > > a file.
>
> > > I often run "patch" and it drops some chunk because it doesn't match,
> > > and it turns out that the miss-match is just one or two lines in a
> > > chunk that could be very big.
>
> > Yes, this would be [: very very :] nice.
>
> Have you people heard about this thing called "branches" ?
>
> - You keep your own code in your own branch.
>
> - You keep Linus's code in a linus branch.
>
> - The patches from Linus always apply to the linus branch.
>
> - You pull Linus's latest updates into your own branch for
> development work, at this point you may need to do some
> merging. Some SCM systems are horrible at merging (CVS)
> while others are really nice (BK).
Description above was basically how to do the merging. Oh, and for
people that have just one brach ("my own tree") patch should be quite
sufficient. Having patch more inteligent at rejects would be win for
everyone.
Pavel
-- (about SSSCA) "I don't say this lightly. However, I really think that the U.S. no longer is classifiable as a democracy, but rather as a plutocracy." --hpa - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/