98218 – Allow a 'Commit and tag as version' when committing files

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 98218 - Allow a 'Commit and tag as version' when committing files

Summary: Allow a 'Commit and tag as version' when committing files

Status:	CLOSED DUPLICATE of bug 44923

Alias:	None

Product:	Platform
Classification:	Eclipse Project
Component:	CVS (show other bugs)
Version:	3.1
Hardware:	All All

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assignee:	platform-cvs-inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2005-06-02 20:36 EDT by Alex Blewitt
Modified:	2007-01-24 06:05 EST (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alex Blewitt

2005-06-02 20:36:04 EDT

When I have a bugfix across a number of files, I often tag the changed files after I have applied the fixes 
to them (and committed them) so that I can find out where bugs were fixed when generating reports on 
the CVS tree.

It would be really handy if the CVS Commit option dialog, as well as adding a commit message, had an 
optional tickbox with 'Tag as version' and a tag identifier. When a bug hits a lot of files (e.g. through a 
refactoring) it's difficult to remember after committing the files which ones have changed, and then 
applying the tag manually afterwards.

I'm guessing that this won't make it into the 3.1 release candidate now, but it's a good an idea to apply 
to any older (or newer :-) versions of Eclipse/CVS as well...

Comment 1 Michael Valenta

2005-06-03 08:26:50 EDT


*** This bug has been marked as a duplicate of 44923 ***

Comment 2 Alex Blewitt

2007-01-24 06:05:10 EST

Whilst this is a dupe (so closing), I don't like the fact that the dupe is REVSOLVED NEVER. It should really be left in an open state if it's not there. Perhaps using a milestone of LATER rather tahn a resolution state of LATER would be more appropriate.