tree configuration ...
On Wed, Jan 20, 2010 at 5:31 AM, Roy Franz wrote:
> On Thu, Jan 14, 2010 at 1:36 PM, Stas Cherkassky
> wrote:
> > Michael,
> >
> > I think you are right - Subversion just wasn't designed for this
> > methodology.
> > But I can't beli
- Great! Make it 'svn cp --sparse --force WC URL' - and we are all set !
[ --force means that we can override file that already exists in the URL,
e.g. by creating a new revision of it, and not issue error message like it
does now ]
On Thu, Jan 14, 2010 at 8:59 PM, Philip Martin
wrote:
> "C. Mic
ry in some fashion so that it could be applied to tags created from
> your working copy? What complications or problems does this introduce in
> your situation? What problems does it alleviate?
>
>
> Stas Cherkassky wrote:
> > Julian,
> >
> > thanks you for your reply.
&g
on for that, but I think it is not clear how a user
> should expect each Subversion command to behave.
>
> In this email I will just address how it works at the moment and how to
> achieve the tagging that you wanted. I will start a separate email
> thread to discuss the semantics of
have like I suggested.
IMHO, this way is more intuitive - that's what unix copy command would do.
regards,
Stas
On Thu, Jan 7, 2010 at 2:42 PM, Julian Foad wrote:
> Stas Cherkassky wrote:
> [...]
>> % svn co $SVNROOT/myproj -–depth empty myproj
>> % svn update -–depth infinity
hat's not a bug but feature, would it be possible
to have a switch to copy command that would behave as I described ?
thanks !
--
Stas Cherkassky
email: scher...@gmail.com
phone: +972-54-4261959
6 matches
Mail list logo
