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

Re: Branching

From: Boelter Markus <Markus.Boelter_at_Micronas.com>
Date: 2004-10-25 16:25:47 CEST

Hi!

>
> >My second issue is a future branch which would be very close
> to one of my existing branches (and more far away from the
> trunk). Does it make sense to make a branch of a branch? Or
> better use the trunk as the source and do much changes to the
> future branch? I guess a branch from a branch would make more
> sense - but I don't want to run into trouble if this is the
> wrong way...
> >
> >
> Branching a branch is never a problem. Perhaps this link (
> http://svnbook.red-bean.com/svnbook-1.1/ch04.html ) might
> prove usefull
> to get some insight on what's best to do. As allways, branching and
> merging are activities that should be done with proper
> preperation and
> planning.

That's why I'm asking. :-) I read this chapter several times,
but was just not sure if it matches to my case. Now I got a
"new" problem:

Before a few mintues I modified a file in the trunk which is
in all branches. After the commit I did a svn up in one of
the branches. The only feedback I got was "At Revision 48" -
noting else. A look in the files showed no modification. svn
up again did nothing.

It seems like the branch recognized a change, made a new
Revision (from 46 to 48), but no changes to the file were made. Why?

When this works I'll do a branch of a branch and look what
will happen :-))

Thanks!
  Markus

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Oct 25 16:26:13 2004

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.