To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=40246





------- Additional comments from [EMAIL PROTECTED] Tue Nov 18 13:28:07 +0000 
2008 -------
beside that the patch is a bit stale meanwhile (ok, i didn't pay too much
attention when it was new...), the applying part isn't the problem. what i don't
like is the generation part that involves too much manual copying.
why not diffing the the changed tree with a reference tree already containing
all patches beside the current change? this difference would make up a new patch
that's generated and just has to be added to the makefile, as in your approach.
what i want to keep is the cycle of change, build that change and create a patch
containing exactly that change. without introducing manual steps that give you a
tree that builds fine but will give you an incomplete patch because you forgot
to copy something to somewhere in advance.

the only drawback i see in that scenario is that you'll only be able to create
new patches. changing existing ones will be a hassle and probably end up in
creating all existing patches from scratch if the overlap is too big.
and yes, it will be slower than gendiff as you always compare the whole tree but
i think it's worth it...

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to