Markus Schaber wrote on Fri, May 13, 2011 at 11:20:11 +0200:
> Hi,
>
> What is the safest future-compatible way to check for an incompatible /
> unknown working copy format which was written by a future subversion
> version? (e. G. WC-NG by SVN 1.7?)
>
> My idea was to run status with depth=empty
On May 13, 2011, at 13:38, Aliasgar Ganiji wrote:
> This is our setup svn 1.6.6 on Linux x86_64. What if the hooks are broken in
> this version? Can someone with this version of svn verify?
The hooks seem to be working correctly for me on Mac OS X 10.6.7 x86_64 with
Subversion 1.6.16 installe
This is our setup svn 1.6.6 on Linux x86_64. What if the hooks are broken in
this version? Can someone with this version of svn verify?
---
Ali
-Original Message-
From: Johan Corveleyn [mailto:jcor...@gmail.com]
Sent: Friday, May 13, 2011 12:29 PM
To: Aliasgar Ganiji
Cc: users@subver
On Fri, May 13, 2011 at 4:40 PM, Aliasgar Ganiji wrote:
> I was in the process of implementing pre-revprop-change and
> post-revprop-change hooks in my company to handle changes to the svnn:log
> property. As per the SubVersion Redbook;
>
> 1. pre-revprop-change should be able to access the
Thanks for quick answer.
Bob Archer a écrit :
I am struggling with an old version of subversion : 1.4.2 Is it
safe for the repository to adopt the 1.6.16 version?
Yes... make sure you svn upgrade the repo or do a dump/load cycle to bring it
up to the newest repository format.
Okay I
> I am struggling with an old version of subversion : 1.4.2 Is it
> safe for the repository to adopt the 1.6.16 version?
Yes... make sure you svn upgrade the repo or do a dump/load cycle to bring it
up to the newest repository format.
> Moreover I want to split an old repos in 2 new repos witho
> On Fri, May 13, 2011 at 4:35 PM, Stephen Butler
> wrote:
> >
> > On May 13, 2011, at 13:41 , K.L. wrote:
> >
> >> Hi,
> >>
> >> Having problems with merge.
> >
> > [...]
> >
> >> me@localhost /srv/www/svnbugs/branches/branch1 $ svn merge
> >> svn+ssh://example.com/var/svn/svnbugs/trunk
> >> ---
Hello,
I am struggling with an old version of subversion : 1.4.2
Is it safe for the repository to adopt the 1.6.16 version?
Moreover I want to split an old repos in 2 new repos without losing
revision of my files :
Old Repo
|--data
|-- test
New Repo 1
| --data
New Repo 2
| --dat
I was in the process of implementing pre-revprop-change and post-revprop-change
hooks in my company to handle changes to the svnn:log property. As per the
SubVersion Redbook;
1. pre-revprop-change should be able to access the intended new value of
the property via standard input. Howeve
2011/5/13 Markus Schaber :
> Hi,
>
> What is the safest future-compatible way to check for an incompatible /
> unknown working copy format which was written by a future subversion
> version? (e. G. WC-NG by SVN 1.7?)
>
In the change log for Subversion 1.6 [1] there is the following line for 1.6.9.
On Fri, May 13, 2011 at 4:35 PM, Stephen Butler wrote:
>
> On May 13, 2011, at 13:41 , K.L. wrote:
>
>> Hi,
>>
>> Having problems with merge.
>
> [...]
>
>> me@localhost /srv/www/svnbugs/branches/branch1 $ svn merge
>> svn+ssh://example.com/var/svn/svnbugs/trunk
>> --- Merging r4 through r5 into '
Hi, Les,
> Von: Les Mikesell [mailto:lesmikes...@gmail.com]
[> ]
> >> What is the safest future-compatible way to check for an incompatible
> >> / unknown working copy format which was written by a future
> >> subversion version? (e. G. WC-NG by SVN 1.7?)
> >>
> >> My idea was to run status with
Hi, Erik,
> Von: Erik Huelsmann [mailto:ehu...@gmail.com]
>
> Hi Markus,
>
> On Fri, May 13, 2011 at 11:20 AM, Markus Schaber software.com> wrote:
> > Hi,
> >
> > What is the safest future-compatible way to check for an incompatible
> > / unknown working copy format which was written by a futur
On May 13, 2011, at 13:41 , K.L. wrote:
> Hi,
>
> Having problems with merge.
[...]
> me@localhost /srv/www/svnbugs/branches/branch1 $ svn merge
> svn+ssh://example.com/var/svn/svnbugs/trunk
> --- Merging r4 through r5 into '.':
> Adir2
[...]
> me@localhost /srv/www/svnbugs/trunk $ svn m
On 5/13/11 7:30 AM, Erik Huelsmann wrote:
What is the safest future-compatible way to check for an incompatible /
unknown working copy format which was written by a future subversion
version? (e. G. WC-NG by SVN 1.7?)
My idea was to run status with depth=empty on the workingcopy root, and
che
Hi Markus,
On Fri, May 13, 2011 at 11:20 AM, Markus Schaber
wrote:
> Hi,
>
> What is the safest future-compatible way to check for an incompatible /
> unknown working copy format which was written by a future subversion
> version? (e. G. WC-NG by SVN 1.7?)
>
> My idea was to run status with depth
Hi,
Having problems with merge.
me@localhost /srv/www $ svn ls svn+ssh://example.com/var/svn/svnbugs
me@localhost /srv/www $ svn mkdir svn+ssh://example.com/var/svn/svnbugs/trunk
Log message unchanged or not specified
(a)bort, (c)ontinue, (e)dit:
c
Committed revision 1.
me@localhost /s
Hi,
What is the safest future-compatible way to check for an incompatible /
unknown working copy format which was written by a future subversion
version? (e. G. WC-NG by SVN 1.7?)
My idea was to run status with depth=empty on the workingcopy root, and
check for SVN_ERR_WC_UNSUPPORTED_FORMAT error
Hi Dear,
I'm using SVN 1.6.15 as my svn server (installed in SUSE 10).
I can checkout, update, commit, import to my svn repositories successfully.
But today, I suffered the error when doing svn commit:
=
svn: Commit failed (details follow):
sv
On May 13, 2011, at 02:00, Markus Schaber wrote:
> As „svn rename“ fails to rename external directories, I currently use the
> following „workaround“:
> - Rename the directory directly on the file system.
> - Change the externals definition in the containing directory to
> poi
Hi,
As "svn rename" fails to rename external directories, I currently use
the following "workaround":
- Rename the directory directly on the file system.
- Change the externals definition in the containing directory
to point to the new destination.
Is this mechanism safe
21 matches
Mail list logo
