It's all about the answers!

Ask a question

Is there anyway to reject a change set?


Tong Li (121) | asked Aug 11 '09, 11:12 a.m.
There is always an accept action for incoming changes, what if I do not want to accept the changes? That is, just reject the changes ( set ) and be done with it.

Thanks.

2 answers



permanent link
Andrew Hoo (1.0k1) | answered Aug 11 '09, 1:10 p.m.
JAZZ DEVELOPER
There is no reject change set action. What do you think 'rejecting' a
change set should do if there were one (what is your work flow that would
want this behaviour?)

The pending changes view shows you the set difference of the change sets
contained in the target stream and in your repository workspace.

If by 'rejecting' you just want to hide the incoming change set then it
poses the problem of not showing you what is really going on. You could
unknowingly be sending yourself down a complicated fork which would then
require a merge, or later you might be confused by why you cant accept
certain things ('caused by a gap of a changeset that you previously
'rejected').

You can use the pending changes view 'Zoom' mode to show only outgoing
change sets if you prefer to work that way.

On Tue, 11 Aug 2009 11:23:00 -0400, tongli
<litong01> wrote:

There is always an accept action for incoming changes, what if I do
not want to accept the changes? That is, just reject the changes (
set ) and be done with it.

Thanks.



--

permanent link
Jean-Michel Lemieux (2.5k11) | answered Aug 11 '09, 4:40 p.m.
JAZZ DEVELOPER
There are two workflows we support, you can (1) reverse a change set, or
(2) replace the stream with the change sets you have.

Option 1 is the best, as it incrementally adds to change histories and
is also what most users are used to doing with other SCM systems where
you can't really change the past, it's done, you can only move forward.

With option 2, you are essentially discarding a bunch of change sets
from a stream, and many of your team members may already have them. So
they have to sync up with you.

I prefer option 1 for small changes, and option 2 when you really want
to backup the entire team to some interesting point in the past.

Cheers,
Jean-Michel


On 8/11/2009 1:10 PM, Andrew Hoo wrote:
There is no reject change set action. What do you think 'rejecting' a
change set should do if there were one (what is your work flow that
would want this behaviour?)

The pending changes view shows you the set difference of the change sets
contained in the target stream and in your repository workspace.

If by 'rejecting' you just want to hide the incoming change set then it
poses the problem of not showing you what is really going on. You could
unknowingly be sending yourself down a complicated fork which would then
require a merge, or later you might be confused by why you cant accept
certain things ('caused by a gap of a changeset that you previously
'rejected').

You can use the pending changes view 'Zoom' mode to show only outgoing
change sets if you prefer to work that way.

On Tue, 11 Aug 2009 11:23:00 -0400, tongli
litong01@us.ibm-dot-com.no-spam.invalid> wrote:

There is always an accept action for incoming changes, what if I do
not want to accept the changes? That is, just reject the changes (
set ) and be done with it.

Thanks.


Your answer


Register or to post your answer.