|
|
Re: Autogenerate patches [message #36051 is a reply to message #35589] |
Fri, 09 November 2007 00:46 |
Eclipse User |
|
|
|
Originally posted by: beatmik.acm.org
Those are good points.
Ali: the way that some of us work around this right now is to manually
do what you are doing, and if we really don't want the change set
sticking around with the outgoing changes we make a patch and attach it
to the bug. It is probably possible for us to make patch creation a one
or two click operation. For example:
152213: support creating patches by dragging change set onto task editor
https://bugs.eclipse.org/bugs/show_bug.cgi?id=152213
While this doesn't provide all the automation that you're after, is this
something that would help you? If so please vote for that bug.
Mik
Mark Phippard wrote:
> On 2007-11-05 10:08:33 -0500, "Ali Burak Kulakli" <kulakli@yahoo.co.uk>
> said:
>
>> I have a simple question. I have a couple of tasks and I need to switch
>> sometimes among them. It would be very helpful that a task can create a
>> patch set of changes and revert source files to original when it is
>> deactivated. And when it is activated, patch can be applied
>> automatically.
>> Is this possible?
>
> I think the spirit behind this request is good, but I am not sure it
> works well enough in reality for Mylyn to try it. For example:
>
> patches do not represent changes to binary files. If you have graphic
> changes you would not want to lose them.
>
> patches do not do a good job with copy/move or directory structure changes.
>
> I think it would be risky for Mylyn to try to take something like this on.
>
> Mark
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02281 seconds