OK, thanks for the information. I think, the most reasonable solution for
me would be a bash script, which just copies the file to be versioned
to my working copy at regular intervals. That should be easy...
> I believe he's thinking of "svnput" whose source is here:
>
> http://svn.apache.org/rep
Ulrich Eckhardt wrote on Thu, Nov 25, 2010 at 14:34:19 +0100:
> On Thursday 25 November 2010, Daniel Shahaf wrote:
> > Ulrich Eckhardt wrote on Thu, Nov 25, 2010 at 09:38:25 +0100:
> > > Now, what makes this special is that in the repository, the marked
> > > foo-test directories don't exist. These
We could implement support for ./foo relative externals, I suppose. It
seems you have a use case for that.
Ulrich Eckhardt wrote on Thu, Nov 25, 2010 at 12:39:15 +0100:
> Hi!
>
> I know that '../name' works as URL, why doesn't './name'? I just want an
> alias
> under a different name, that's a
On Nov 25, 2010, at 07:49, Ewgenij Sokolovski wrote:
>> 2. You turn the directory where the file is stored a working copy.
>> You can do so by simply creating a target dir in the repository
>> ("svn mkdir $URL/config") and checking out that dir in the
>> directory where the file is stored ("svn co
> The short answer is "no".
Any way hardlinks/symlinks could help?
E.g. symlinking an out-of-working-copy-file to a working-copy-file?
>I hope I guessed right what you meant.
Yes, you did :)
> 1. You create a solution on top of SVN.
> This means e.g. writing a batchfile that creates or syncs a WC with the
> according configuration file. You might also be able to employ symlinks or
> other features of your filesystem to your
On Thursday 25 November 2010, Daniel Shahaf wrote:
> Ulrich Eckhardt wrote on Thu, Nov 25, 2010 at 09:38:25 +0100:
> > Now, what makes this special is that in the repository, the marked
> > foo-test directories don't exist. These directories are just file-system
> > copies of foo which I made in or
Note up front: You are mixing up the terms "repository" and "working copy" in
your message, I hope I guessed right what you meant.
On Thursday 25 November 2010, Ewgenij Sokolovski wrote:
> I have the following issue. I would like to version a configuration file,
> which resides outside of my svn-
Hello, list. I have the following issue. I would like to version a
configuration file, which resides outside of my svn-repository. It is a system
configuration file, so it has to be stored at a predefined place. Certainly, I
could copy it to my repository and version it there. But that would imp
Hi!
I know that '../name' works as URL, why doesn't './name'? I just want an alias
under a different name, that's all. Current workaround is that I
use '../parent/name' instead.
Uli
--
ML: http://subversion.apache.org/docs/community-guide/mailing-lists.html
FAQ: http://subversion.apache.org/f
On Thursday 25 November 2010, Daniel Shahaf wrote:
> Have you tried both 'cd projects; svn up foo-test-1' and 'cd
> projects/foo-test-1; svn up'?
Neither, just right-clicking on the folder and selecting
TortoiseSVN->Update. ;) I'll try to find out which SVN equivalent that is.
> > I also thought
Ulrich Eckhardt wrote on Thu, Nov 25, 2010 at 09:38:25 +0100:
> Greetings!
>
> I have a scenario where I can't update a working copy while an update on an
> unrelated other working copy is in progress. The directory structure looks
> like this:
>
> projects/
> foo
> foo-test-1 *
>
Hi group,
We have a product development structure that looks a bit like below :-
trunk
Design
Module_A
file_bundle_x_source
Module_B
file_bundle_y_source
Verification - (externals)
Simulation_1
file_bundle_x
Simulation_2
file_b
Greetings!
I have a scenario where I can't update a working copy while an update on an
unrelated other working copy is in progress. The directory structure looks
like this:
projects/
foo
foo-test-1 *
foo-test-2 *
lib_bar
Now, what makes this special is that in the rep
14 matches
Mail list logo
