- yeah, that's the capability I miss compared to any other SCM system I know
(which is CVS, Perforce, and now - a little of git).
Add it to other smaller but also annoying things, and I am half the way into
git manual... Git has handy submodules which can be brought together into
any tree configura
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 believe SVN users don't have the same problem. I wonder how they
> solve it ...
We have the same problem, but our 'solution' is to j
-Original Message-
From: C. Michael Pilato [mailto:cmpil...@collab.net]
Sent: Thursday, January 14, 2010 11:57 PM
To: Stas Cherkassky
Cc: Julian Foad; dev@subversion.apache.org; Strahovsky, Ido
Subject: Re: suspected bug report or feature request - tagging a sparse
directory
I suspect th
I suspect that most folks that have this problem had it long before sparse
checkouts was introduced as a feature. I mean, there's nothing about sparse
checkouts that's specific to the goal you have in mind, right? So I suspect
those that have come before you have taken an additive approach to the
- 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
Michael,
I think you are right - Subversion just wasn't designed for this
methodology.
But I can't believe SVN users don't have the same problem. I wonder how they
solve it ...
In other words, the sparse tag is just a mean to achieve what I need, which
is a communication
between sub-module designe
"C. Michael Pilato" writes:
> Stas, you are quite right that the messaging here is important, if only to
> avoid hurt feelings. Your use-case is a valid one, and we'd all do well not
> to discount it. But Subversion simply wasn't designed to accommodate it.
> And this isn't even a small "oops w
Stas, you are quite right that the messaging here is important, if only to
avoid hurt feelings. Your use-case is a valid one, and we'd all do well not
to discount it. But Subversion simply wasn't designed to accommodate it.
And this isn't even a small "oops we overlooked it" thing. This is a
fun
Julian,
thanks you for your reply.
Your approach may technically work, but, I am afraid, it's not realistic in
real large project.
The [everything except dirA and dirB] part may be quite complicated for
large sparse tree.
The second approach (multiple svn cp WC URL) is also cumbersome and requir
Hi Stas.
Your question raises an important issue: "What are the semantics of
sparse directories?" You expected "svn copy" to copy just the parts that
are present in the WC, whereas in fact it copies the whole logical tree.
There is a reason for that, but I think it is not clear how a user
should e
On Fri, Jan 8, 2010 at 1:31 AM, Stas Cherkassky wrote:
> Julian,
>
> I don't want to remove parts of the tree from the repository.
> What I want is, effectively, a way to independently mark separate
> parts of the tree with the same tag.
> (I tried to explain it in my example). I don't see how you
Julian,
I don't want to remove parts of the tree from the repository.
What I want is, effectively, a way to independently mark separate
parts of the tree with the same tag.
(I tried to explain it in my example). I don't see how your method
(using svn rm) does it.
If a tag is a property of a file
Stas Cherkassky wrote:
[...]
> % svn co $SVNROOT/myproj -–depth empty myproj
> % svn update -–depth infinity myproj/dirA
>
> .. modifies it in some way and tries to tag:
>
> % svn mkdir $SVNROOT/tags/rel_X
> % svn copy myproj $SVNROOT/tags/rel_X/ -m “tagging part A of myproj
> for the next integ
Hi,
I have a problem with tagging a sparse directory.
Suppose I have this structure:
myproj
dirA
...
dirB
...
I want user A to work on dirA, and user B - on dirB.
But both are contributing to the same release-candidate, let's call it rel_X.
(the idea is that integrator would b
14 matches
Mail list logo
