[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Finding out latest revision in a branch

From: Shridhar Daithankar <ghodechhap_at_ghodechhap.net>
Date: 2005-05-11 14:36:23 CEST

On Wednesday 11 May 2005 5:04 pm, Ben Collins-Sussman wrote:
> On May 11, 2005, at 6:11 AM, Shridhar Daithankar wrote:
> The 'head' of all branches is simply the global HEAD revision, right?

Right.
>
> You can use 'HEAD' as a revision number on the commandline. But if
> you want to know the actual value of HEAD at this moment, a simple
> 'svn status -u' will show that on the last line it prints.

That is head...:-(

OK. Let me describe the details.

- In working copy, I do a svn log, I get following revisions,
1,4,5,78,79,81,82 with branch creation on revision 78.

- Revision 82 is a patch merge and has nothing to do with the feature for
which the branch was created. So I don't want it. So I need to look at 81.
(The patch was merge in a hope that ultimately I will merge three svn
branches in one SVN branch. But right now, I am merging 3 svn branches into
another SCM by hand.)

The diff 78:82 is 768517 lines which is hell lot more than I can account for.
but at least it mentions that it is diffing between 78 and 82.

The diff 78:81 is 765087 lines but it mentions that it is diffing revision 0
and 81!!.

And this is the bit that disturbs me. It gives me a feeling that I don't know
what is happening.

Is there a way where I can see the branch progress. AFAIU, you can get history
of either file or directory but not the branch as such. And I don't have hook
emails etc. set up to refer to.

Any help is appreciated. TIA.

 Regards
  Shridhar

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed May 11 15:01:15 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.