Hi David,
the cause is your shell expanding the * to the list of all files in the
directory before invoking the command. So in a directory containing the files
foo, bar and baz.txt, the command "svn add *" actually translates to "svn add
foo bar baz.txt" before the command is executed. Svn neve
David,
On Fri, Aug 27, 2010 at 3:59 PM, David H wrote:
>
> As a new user it was my expectation that 'svn add *' called from within the
> root
> of my version-controlled root directory would result in *all* changes that
> had been
> made within the file system to be scheduled for inclusion on th
Subversion Dev team:
Thanks for all your hard work. I just began using subversion and it is
great.
Among other things, it is fast.
One complaint.
I'm using a Linux system, fyi.
As a new user it was my expectation that 'svn add *' called from within the
root
of my version-controlled root direct
On 08/11/10 13:46, Lieven Govaerts wrote:
> On Wed, Aug 11, 2010 at 8:28 PM, Gero wrote:
>> On Wed, 2010-08-11, Lieven Govaerts wrote:
>> On Wed, Aug 11, Gero wrote:
Hi,
After moving to a new system (Kubuntu Hardy -> Lucid) I can no longer
access
an SVN repository:
>>
On 08/24/10 14:30, bebop52 wrote:
> I checked out a Latex-Project from Google-Code Projecthosting, using
> subversion, for which I installed a client on my Ubuntu Lucid
> machine. Now I want to work to use emacs to edit the projectfiles and
> to commit the changes to the Google-Code repository.
>
On Fri, Aug 27, 2010 at 7:13 AM, Neson Maxmelbin (RBEI/EMT5)
wrote:
>
> Hello Guys,
>
> I have setup SVN 1.6 with Apache 2.9 on Windows Server 2003 SP2 with LDAP
> conf.
>
> I can access the repositories ok, but unable to view the parent path on web
> so that I can see the list of repositories.
>
>
Linedata Limited
Registered Office: 85 Gracechurch St., London, EC3V 0AA
Registered in England and Wales No 3475006 VAT Reg No 710 3140 03
-Original Message-
> From: Bob Archer [mailto:bob.arc...@amsi.com]
> Sent: 26 August 2010 17:47
> To: Giulio Troccoli; users@subversion.apache.or
The easiest way to verify is to run svn upgrade again. If it succeeds
without an error it is at the last version.
If you want to look further you can check the format file in the root of the
repository and with fsfs in its db subdirectory.
For my just created 1.6 repository I see version 5