This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Show change sets | ||
---|---|---|---|
Product: | versioncontrol | Reporter: | artisan <artisan> |
Component: | Subversion | Assignee: | issues@versioncontrol <issues> |
Status: | REOPENED --- | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | PC | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
artisan
2009-08-18 09:10:37 UTC
the files listed in the table given by "Show changes" are such which are new or modified and aren't commited yet - so what revision/msg/author do you want to see? the one from the base revision? what would be the extra value in that? thanks What I meant is to add a level in the list of changes. Currently this list is purely file based. What would be very helpful is to put these changes in the context of a commit - for incoming changes. Suppose since my last update I've had 10 people who has modified each 100 files. I would see a list of 1000 lines in the dialog. For somebody who's just adding code that's ok. For somebody who's monitoring at some level it is not. To check what people have done since the last update it would be incredibly helpful to see a chronological list of commits. Together with the name, date and comment. This way, if I need to check whether the expected changes were done, I can see this in the list of commits. This information can not be deduced from a list of 1000 items. And if I were to do code review of a commit, I can expand the commit item and see the files which were included into the commit. I would be able to see right away if it's logical these precise files were (not) changed. And if I check each file for changes I would be able to check the validity of the change based on the comment of the commit. So it's really about making the "Show Changes" dialog usable to people who need to keep an eye on the code of the complete application. I hope this help. :-) > For somebody who's monitoring at some level it is not.
> To check what people have done since the last update it would be incredibly
> helpful to see a chronological list of commits. Together with the name, date
> and comment. This way, if I need to check whether the expected changes were
> done, I can see this in the list of commits. This information can not be
> deduced from a list of 1000 items.
well, yes, i think i understand, but did you try the "show history" view?
or is it that you want to see the files history in the context of commit you are just about to make?
hi, any update on this? taken from reporters mail: Not exactly : this ticket is about showing commits at the highest level with the files in them instead of the inverse. As I mentioned it's not exactly useful for the average developer but certainly for someone reviewing the code changes - already checked out or not. |