Opened 6 years ago

Last modified 5 years ago

#2413 new enhancement

CVS incremental update uses -d option which might have unfortunate side effects

Reported by: daviddev Owned by:
Priority: patches-accepted Milestone: 0.9.+
Version: 0.8.7p1 Keywords: cvs


As per the cvs man page, in relation to the "update -d" option:

"This is useful for updating directories that were created in the repository since the initial checkout; but it has an unfortunate side effect. If you deliberately avoided certain directories in the repository when you created your working directory (either through use of a module name or by listing explicitly the files and directories you wanted on the command line), then updating with -d will create those directories, which may not be what you want."

Pros of -d:

  • If a new subdirectory was created in the directory of your checkout, then it will automatically be created.

Cons of -d:

  • The unfortunate side effect mentioned in the manual.
  • New module dependencies will not be created (these would translate into new subdirectories) because it's only when doing a checkout, that module dependencies (stated through the file CVSROOT/modules) will be resolved.

In my particular case, using this option effectively messes up my working dir, so I'll be removing it in my server, but maybe someone has a better idea?

Change History (2)

comment:1 Changed 6 years ago by tom.prince

  • Milestone changed from undecided to 0.8.+
  • Priority changed from minor to patches-accepted

comment:2 Changed 5 years ago by dustin

  • Milestone changed from 0.8.+ to 0.9.+

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.