top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

What is head revision and specific version in SVN?

0 votes
409 views

Can anyone give me what is useful and when we actually use?

posted Aug 30, 2018 by anonymous

Looking for an answer?  Promote on:
Facebook Share Button Twitter Share Button LinkedIn Share Button

Similar Questions
+2 votes
SVN: Unexpected behaviour when checking out a copy at an invalid revision

Checking out a copied directory at a revision prior to the copy results in a checkout of the data before the copy. I would expect this to fail in the same way that attempting to update to an invalid revision fails.

Is this the intended behaviour? If so, shouldn't there be some message that your working copy is using a different location than requested?

 > svn copy trunk mybranch -m 'copy test'
Committed revision 2

 > svn co mybranch -r1 mybranch

 > svn info mybranch
Relative URL: ^trunk

Checking out the branch at a valid revision then attempting to update to the earlier revision results in an error:

 svn: E160005: Target path 'mybranch' does not exist

(I was attempting to checkout the revision given by 'Last Changed Rev' from 'svn info' on a child of a copied directory - it points at a revision before the copy, but that's a different discussion)

+5 votes
Can svn merge --record-only be applied multiple times on a revision number?

Are there side effects from applying the same svn merge --record-only on the same revision number and a new commit each time it is applied ?

Would there be issues with SVN mergeinfo and/or SVN in general if one keeps applying svn merge --record-only on a revision number repeatedly and commit in a svn merge --record-only followed by commit followed by svn merge --record-only followed by commit and the next cycle begins ? Its not an infinite loop svn merge; it would stop at some point.

0 votes
How to check which branches have specific commit in SVN?

We have an svn repository with several branches and tags. 

- trunk/
- branches/
 - stable_1
 - stable_2
 - etc.
- tags/
 - stable_1_release_a
 - stable_1_release_b
 - etc.

We develop our software in trunk (or in a development branch which will be reintegrated to trunk). We merge the changes from trunk to a stable branch. Sometimes we discover a bug which has been introduced quite some time ago. Because the list of branches becomes quite long, I would like to know if it is possible to easily see in which branches / tags the bug is?
So if for instance the bug was introduced in r50 in trunk and currently we are at r100, is there an svn command to see which branches / tags have r50 of trunk merged?

+1 vote
svn log hang after upgrade from version 1.7.5 to 1.8.3

I recently upgraded my Subversion client from version 1.7.5 to 1.8.3 and from that time on I experience hangs when executing multiple 'svn log' commands in a short amount of time. The "hanging" svn process consumes all CPU cycles it gets but never finishes.

I can reproduce the problem using the following shell script (on Windows using Cygwin):

#!/bin/bash
ROOT="http://example.com/svn/trunk"
for DIR in $(svn ls "${ROOT}" | head -n 4); do
 svn log -v -l 5 "${ROOT}/${DIR}" 2>&1 | head -n 100 > /dev/null
done

In my environment I need at least 4 svn processes to achieve the faulty behavior. The hang only occurs if the output is truncated using the head command (but it can be redirected to a normal file instead of /dev/null which then contains the expected log messages).

...