|
Actions:
|
2012-01-18 19:31 AEST by Arthur Barrett - I've speculated previously that CVSMANAGER should have a sqlite database for things like val_tags (see
bug 6012 and 6051).
If this database existed then we could 'delete' branches, by simply listing them as 'deleted' (then
excluding that branch name from the list generated by Log). This wouldn't really allow you to re-use
the branch name as a new tag name, or create a new branch with that name... Alternatively 'delete'
could 'rename' the actual branch in the RCS file to some artificial name, and then 'hide' that name.
We could rename the same way. Create an alias, and delete the original name. |
|
|
2012-01-19 01:38 AEST by Glen Starrett - I'd call it "remove" to be consistent with the regular remove function.
Changing the name to "#REMOVED_old-branch-name_GUID" then filtering out the
#REMOVED_* names would work.
Would you also need to filter out removed branches from e.g. revision graph?
That might imply removing the revisions from log output.
Another thing to consider -- are all tags created on that branch (either branch
or regular tags) also removed in a cascade or just the versions are short
circuited out?
Having that though brings to mind that you might want to recover or alias based
on an existing one, so there should be a function to get the names, including
deleted ones, something like "cvs log -a" (a for all, like "ls -a" or the effect
of "dir /a").
|