| cvs update [message #255369] |
Fri, 02 May 2008 13:30  |
Eclipse User |
|
|
|
Hello,
Is there a way to create patches from incoming changes? For example, I
want to review changes done by my coworker at a later date. So I update my
code. But in doing so, I loose track of all changes. When I synchronize
with repository again, there are no changes. I want to be able to save
their incoming changes as a patch, update so that my code is up to date
and then review their patch at a later date.
Is that possible? Maybe there are workarounds. One would be to ask them to
create a patch before submitting which I can use later?
Thanks.
|
|
|
| Re: cvs update [message #255373 is a reply to message #255369] |
Fri, 02 May 2008 13:40  |
| Eclipse User |
|
|
|
Originally posted by: codeslave.ca.ibm.com
1. Switch Synchronize view to Change Sets presentation (that's the view
toolbar button that looks like a folder tree).
2. Select a change set, right-click, and do Open Change in Compare
Editor. Now you can review an entire set of commits for someone on your
team, assuming they're grouped by matching commit comment.
Not sure if this is new in Eclipse 3.4 or requires Mylyn 2.3, but it
works for me here.
Nick
Upkar Lidder wrote:
> Hello,
>
> Is there a way to create patches from incoming changes? For example, I
> want to review changes done by my coworker at a later date. So I update
> my code. But in doing so, I loose track of all changes. When I
> synchronize with repository again, there are no changes. I want to be
> able to save their incoming changes as a patch, update so that my code
> is up to date and then review their patch at a later date.
> Is that possible? Maybe there are workarounds. One would be to ask them
> to create a patch before submitting which I can use later?
>
> Thanks.
>
|
|
|
|
| better workflow for using cvs / reviewing patches (was Re: cvs update) [message #255380 is a reply to message #255369] |
Fri, 02 May 2008 16:34 |
| Eclipse User |
|
|
|
Originally posted by: codeslave.ca.ibm.com
I suppose a revised workflow might help:
a - your colleague(s)
b - you
(a) make patch(es) from the OUTGOING changes before committing them
(a) attach them (and optionally, Mylyn context) to the affected bug(s)
(b) receive notification of the update(s) to the bug(s)
(b) review patch(es) / apply task contexts & apply those deemed worthy.
Or, if you're just reviewing for information to know what's changed
rather than to approve/deny the changes:
(a) make patch(es) from the OUTGOING changes before committing them
(a) attach them (and optionally, Mylyn context) to the affected bug(s)
(a) commit them
(b) receive notification of the update(s) to the bug(s), and review
patch(es) / apply task contexts
Nick
Upkar Lidder wrote:
> Hello,
>
> Is there a way to create patches from incoming changes? For example, I
> want to review changes done by my coworker at a later date. So I update
> my code. But in doing so, I loose track of all changes. When I
> synchronize with repository again, there are no changes. I want to be
> able to save their incoming changes as a patch, update so that my code
> is up to date and then review their patch at a later date.
> Is that possible? Maybe there are workarounds. One would be to ask them
> to create a patch before submitting which I can use later?
>
> Thanks.
>
|
|
|
Powered by
FUDForum. Page generated in 0.08435 seconds
Home