When creating a new topic, if values for start tag and
module are given, and no value for an end tag is
supplied, take the requested version from the repository
and load it like you would for a plain text upload.
Is there a "cvs rdiff" command that we can use to retrieve
the text you are talking about, or would we need to retrieve
each file in turn and treat it (for the purposes of the
review) as a new file?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
An rdiff with a start tag of anything and an end tag of 1.0
works. For example:
cvs rdiff -u -r FOO-1_2 -r 1.0 xxx
I use the existing system in this manner. The only drawback
is that the view form highlights all of the text for version FOO-
1_2 as "removed" and shows an empty column for version
1.0. The desired result would show version FOO-1_2 without
highlighting and not display a column for version 1.0.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I also would like something like this. When adding new
files to the project (which is quite often at the beginning
of the project), you don't want to review diffs, you want to
review the entire file. For us, this is most often the case
because peer reviews of changes to files that have already
been peer reviewed are often not required. I know I can
upload the file, but if it is in the repository and I know
the tag or version of the file that should be reviewed, I
should be able to enter that without having to upload the file.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The has been implemented and is available now in CVS, and
will be available for version 1.8.4. Here is the CHANGELOG
entry:
* It is now possible in the create topic screen to only
specify a
single tag and a module name in order to create a new
topic, rather
than both the start and end tags, with the module name.
The effect
of a single tag is to create a topic with the full
contents of all
tagged files in the specified module.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=208928
Is there a "cvs rdiff" command that we can use to retrieve
the text you are talking about, or would we need to retrieve
each file in turn and treat it (for the purposes of the
review) as a new file?
Logged In: YES
user_id=1029599
An rdiff with a start tag of anything and an end tag of 1.0
works. For example:
cvs rdiff -u -r FOO-1_2 -r 1.0 xxx
I use the existing system in this manner. The only drawback
is that the view form highlights all of the text for version FOO-
1_2 as "removed" and shows an empty column for version
1.0. The desired result would show version FOO-1_2 without
highlighting and not display a column for version 1.0.
Logged In: NO
I also would like something like this. When adding new
files to the project (which is quite often at the beginning
of the project), you don't want to review diffs, you want to
review the entire file. For us, this is most often the case
because peer reviews of changes to files that have already
been peer reviewed are often not required. I know I can
upload the file, but if it is in the repository and I know
the tag or version of the file that should be reviewed, I
should be able to enter that without having to upload the file.
Logged In: YES
user_id=208928
The has been implemented and is available now in CVS, and
will be available for version 1.8.4. Here is the CHANGELOG
entry:
* It is now possible in the create topic screen to only
specify a
single tag and a module name in order to create a new
topic, rather
than both the start and end tags, with the module name.
The effect
of a single tag is to create a topic with the full
contents of all
tagged files in the specified module.