On Mon, 1 Dec 2008, Bailey, Darragh wrote:
> I don't think that is very practical. Can you imagine the problems
> where changes are needed to the patch or the whole fix needs to be
> changed to go a completely different direction? The patch is
> already committed so the next change has to be layered on top of
> it. So unless you have a separate branch for each and every change,
> then you have the problem of dealing with merging multiple
> potentially non-consecutive revisions onto the target branch. I
> think that would quickly become a mess.
If you're thinking of ways to make patch management easier, then
things like 'git' and 'quilt' are really good at tracking
re-arranging patches (e.g. the 'cherry-pick' command in 'git' rocks).
(NB: I havn't used quilt, but it's designed precisely for tracking
patches).
regards,
--
Paul Jakma paul at clubi.iepaul at jakma.org Key ID: 64A2FF6A
Fortune:
For every problem there is one solution which is simple, neat, and wrong.
-- H. L. Mencken
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!
