Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Philipp Marek <philipp <at> marek.priv.at>
Subject: Branching/Tagging in fsvs
Newsgroups: gmane.comp.sysutils.backup.fsvs.general
Date: Monday 17th December 2007 10:20:36 UTC (over 9 years ago)
Hello everybody,


I would like to ask for a bit of opinion ... I'm currently thinking about
"branch" and "tag" commands, and wouldn't mind some feedback.

For single URL operation they'd be easy:
- With a single argument (but no URL), it would simply do a substitute
  of "/trunk/" to "/tags/%s/" (both configurable) on the base URL, and
  do a copy from the base URL (ie. the currently committed state) to the
  calculated URL - that should catch at least 99% of all cases.
- With a single URL argument, the copy would be done to there
  (repos to repos, again).
- With two arguments, one being a path (like "."), this path would get
  committed to the target URL (2nd value) - by using copyfrom, if
  possible.

So far, so good ... no problems.


But for schemes using more than a single URL ... Should a branch/tag
do a "mixed" copy in there, ie. re-create the working copy directory?
The (common) base URL could be defined via some option, so that the
parameter (branch or tag name) would simply be appended.

Or is it better to just copy each URL to its own branch/tag directory?
That would mean that the working copy has to be constructed again for
testing - but would be far easier.


Maybe the "merging" copy should be a new command, like "merge-urls-to"
or something like that ... (any better ideas for the name)?


Would that make sense? Any other ideas, wishes, or other feedback?


-- 
Versioning your /etc, /home or even your whole installation?
             Try fsvs (fsvs.tigris.org)!
 
CD: 3ms