Mark Phippard wrote:
>> I don't remember when exactly it had been added. In 3.1M2 they've
>>added outgoing commit sets, which could be confusing, but may appear
>>handy if you get use to it. I was referring to incoming commit sets
>>(grouping changes with the same comment), which probably was in 3.0.
> Subversion commits truly are grouped together by the revision number.
Right, but currently you can't see comment per that group. Moreover,
if there was more then one commit you can't really see what changed
files belong to each commit (not before you'll open change on resource
history view, which provide slightly different slicing and does not
allow to pickup updated files).
> What is it that you would need here, or be looking for? Off the top of my head
> is it something like there have been 10 revisions, involving 50 files since
> you last updated. And when you do Synch you could pull in changes by the
> revision/commit set, as opposed to just examining the 50 changes? I
> haven't used CVS since 2.x so I do not know about this feature.
Yes, something like that. You can see description for each group of
changes and can choose to update few files from the group of update
entire group (that is what I usually do after reviewing changes).
BTW this cover big chunk of functionality of tools like FishEye or
TMate in terms of monitoring/reviewing incoming changes.
Received on Tue May 24 12:08:07 2005