Databases
StackOverflow2013
Postsdbo
POHow to check out a CVS branch point?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to check out a CVS branch point?
    text
    copied!<p>First, I have to admit I screwed up a little with CVS. I had a release tag <code>releaseX</code>, which was done some time back (i.e., not HEAD). Then I decided I need a maintenance branch at that point. Instead of creating a branch tag (<code>branchX</code>) in <em>addition</em> to <code>releaseX</code>, I <em>deleted</em> the release tag and created a branch tag (erroneously) named <code>releaseX</code>. I then proceeded to work on that maintenance branch, and created <code>releaseX1</code>, <code>releaseX2</code> etc.</p> <p>My problem: when I check out <code>releaseX</code>, I get the <em>branch head</em>, i.e. the latest code from that branch. What I <em>need</em> now is the code <em>at the branch point</em>, i.e. the <em>former</em> <code>releaseX</code> code.</p> <p>Is there any way to do this?</p> <p>Reverting to earlier repository version from backup is not an option.</p> <p><strong>Edit:</strong> I know I can work around it by doing a date-based checkout. I would like to know if it's possible to still do a tag-based one.</p> <p><strong>Update</strong> (Re @Philip Derbeko): I know that CVS does not correlate between files. But CVS <em>does</em> have the information where the branch occured. In ViewVC, I can even see it:</p> <p><code>File X - Revision 1.y - Branch: MAIN - Branch point for: releaseX</code></p> <p>The next file revision is:</p> <p><code>File X - Revision 1.y.2.1 - Branch: releaseX - CVS Tags: releaseX1</code></p> <p>The metadata is apparently there. Hence my question: <strong>Is it possible to check out the branch <em>point</em>, not the branch <em>HEAD</em>?</strong></p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload