> -Original Message-
> From: Andreas Krey [mailto:a.k...@gmx.de]
> Sent: dinsdag 12 juli 2011 10:07
> To: Geoff Hoffman
> Cc: Subversion
> Subject: Re: Doing svn checkouts on top of svn checkouts?
>
> On Tue, 12 Jul 2011 00:30:06 +, Geoff Hoffman wrote:
&
> -Original Message-
> From: Daniel Shahaf [mailto:d...@daniel.shahaf.name]
> Sent: dinsdag 12 juli 2011 5:47
> To: Nico Kadel-Garcia
> Cc: Geoff Hoffman; Subversion
> Subject: Re: Doing svn checkouts on top of svn checkouts?
>
> Nico Kadel-Garcia wrote on Mo
On Tue, 12 Jul 2011 00:30:06 +, Geoff Hoffman wrote:
...
> To clarify what I meant - say you have Repo-A/Path-B and Repo-X/Path-Y. You
> could cd into your working copy of Path-B and do svn checkout Repo-X/Path-Y
> Y and end up with B/Y in your working copy such that changes under Y commit
> to
>
> Geoff Hoffman wrote on Mon, Jul 11, 2011 at 18:20:41 -0700:
> > This is a feature, yes. Subversion does allow your working copy to point
> to
> > more than 1 svn path.
> >
>
On Mon, Jul 11, 2011 at 7:21 PM, Daniel Shahaf wrote:
> Geoff: you cannot point a single working copy item at more tha
Nico Kadel-Garcia wrote on Mon, Jul 11, 2011 at 23:42:07 -0400:
> On Mon, Jul 11, 2011 at 10:21 PM, Daniel Shahaf
> wrote:
> > Geoff: you cannot point a single working copy item at more than one URL.
> > (well, unless you create two externals with the same target file. Don't
> > do that.)
> >
>
On Mon, Jul 11, 2011 at 10:21 PM, Daniel Shahaf wrote:
> Geoff: you cannot point a single working copy item at more than one URL.
> (well, unless you create two externals with the same target file. Don't
> do that.)
>
> Nico: explain /exactly/ what you have been doing (best: a script(1)
> transcr
Geoff: you cannot point a single working copy item at more than one URL.
(well, unless you create two externals with the same target file. Don't
do that.)
Nico: explain /exactly/ what you have been doing (best: a script(1)
transcript). I don't know if you are complaining about nested working
cop
On Jul 11, 2011, at 21:05, Geoff Hoffman wrote:
> (This list is reply-above isn't it?)
Not usually:
http://subversion.apache.org/docs/community-guide/mailing-lists.html#top-posting
Oh, I completely agree -- in the vast majority of cases you definitely want
to avoid doing it. I'm just explaining why it doesn't throw errors at you.
Cheers -
(This list is reply-above isn't it?)
On Mon, Jul 11, 2011 at 7:00 PM, Nico Kadel-Garcia wrote:
> On Mon, Jul 11, 2011 at 9:20 PM, Geo
On Mon, Jul 11, 2011 at 9:20 PM, Geoff Hoffman
wrote:
> This is a feature, yes. Subversion does allow your working copy to point to
>> 1 svn path.
> Sounds a lot like when you use svn:externals. This may be the more
> "standard" way of achieving what you're talking about.
> If you change code in [
This is a feature, yes. Subversion does allow your working copy to point to
> 1 svn path.
Sounds a lot like when you use svn:externals. This may be the more
"standard" way of achieving what you're talking about.
If you change code in [yourstuff] and [stuff pointing back to external's
home] then w
I just ran into a fascinating configuration where someone is doing
Subversion checkouts on top of existing Subversion checkouts. I'd
never even *THOUGHT* of pulling such a stunt, but it's apparently
workable.
I'm concerned, though, that any change in the source of the Subversion
checkout to a bran
12 matches
Mail list logo