Andy Levy <andy.levy@gmail.com> wrote:
> On 2/5/07, Hendrik Schober <SpamTrap@gmx.de> wrote:
> > Andy Levy <andy.levy@gmail.com> wrote:
> [...]
> > If my working copy looks like this
> >
> > project1
> > |
> > +-prj1_stuff1
> > |
> > +-prj1_stuff2
> > |
> > +-shared1
> > |
> > +-shared2
> >
> > can I then throw the same tag across that shared
> > stuff as well?
>
> No, because a tag is nothing more than a copy. [...]
>
> [...]
>
> > Yikes. IIUC, I cannot even checkin changes in
> > "shared[N]" automatically when I checkin changes
> > to "project1", but have to go through all the
> > externals and do this manually. Is that true or
> > did I understand this wrong? If so, that's going
> > to be a serious problem.
>
> Recall that externals can point at different repositories just as
> easily as they can the same repository. You can't have an atomic
> commit against more than one repository.
> [...]
Ugh. What now?
We'd /really/ like to switch to svn. Hwoever, we would
need some way to use it so that it fits our needs, not
the other way around.
Lemme recap:
We have several projects considerable parts of which
are shared between them. Developers are hacking away
on those projects including the shared code, and have
to check in changes in the shared parts as well as in
the project-specific parts of the code. When projects
get tagged, the shared parts should get the same tag.
Any ideas out there?
Schobi
--
SpamTrap@gmx.de is never read
I'm HSchober at gmx dot org
"My hope is that if more people start reading books,
the world will become a better place."
froarulv in afp
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 8 11:54:37 2007