Hello,
I've found a bug when dumping a certain part of an existing repository (having
~2000
commits, ~15 are of interest for the other one) into another existing
repository (having
already ~130 commits) using the following syntax (on Win7 x64):
svnadmin dump .\desktop\OldRepo --incremental |
On Wed, Feb 20, 2013 at 08:21:57AM +0100, sven.m...@ltb-berlin.de wrote:
> Hello,
>
> I've found a bug when dumping a certain part of an existing repository
> (having ~2000
> commits, ~15 are of interest for the other one) into another existing
> repository (having
> already ~130 commits) usin
Yes, so long as you never check out ^/ or ^/tags/ (ie, parents of the
"QA"-"qa" clash).
Les Mikesell wrote on Tue, Feb 19, 2013 at 15:57:58 -0600:
> We have a project with some with paths like tags/QA/ that were
> created manually - for a mostly windows application. Now we'd like
> to start
> Dear all,
>
> I am not sure if this is a bug or I am missing something. But I just found a
> very
> unusual situation.
> Please refer to the screenshot below:
>
>
>
> Both parts in the above screenshot refer to the same revision in the same
> repository.
> The first part from the screenshot
The "svn list" command does not list directory entries if they are
svn:externals.
Assuming this is by design, is there a way for it list externals also?
On Wed, Feb 20, 2013 at 10:02 AM, C M wrote:
> The "svn list" command does not list directory entries if they are
> svn:externals.
>
> Assuming this is by design, is there a way for it list externals also?
>
cd into the local directory defined by your external, then svn list there.
--
Conne
C M writes:
> The "svn list" command does not list directory entries if they are
> svn:externals.
>
> Assuming this is by design, is there a way for it list externals also?
The Subversion 1.8, the next release, currently has
$ svn ls http://localhost/repo --include-externals
A/
Listing externa
But that means I have to create a working copy. I don't necessarily want to
do that if all I am looking for is a directory listing.
On Wed, Feb 20, 2013 at 11:06 AM, Geoff Hoffman
wrote:
>
>
> On Wed, Feb 20, 2013 at 10:02 AM, C M wrote:
>
>> The "svn list" command does not list directory entrie
It seems that SVN does not tag svn:externals.
We have defined a structure such that child projects have link from a
parent project.
Parent project -> child project_1
-> child project_2
-> child project_3
However, when you go to tag a release for a chil
Externals are separate repositories by design. You should reference
externals to a specific revision, or tag the externals first and rewrite
your externals to point to the tagged externals.
On Wed, Feb 20, 2013 at 10:28 AM, C M wrote:
> It seems that SVN does not tag svn:externals.
>
> We hav
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailin
Some clients like TortoiseSVN have a feature that will pin the external to the
revision you are copping when doing the tag. Otherwise, you have to do it
manually before or after you create your tag.
From: C M [mailto:cmanalys...@gmail.com]
Sent: Wednesday, February 20, 2013 12:29 PM
To: users@s
The external definitions do specify a revision. That part is working fine.
I am just not clear on why a simple copy (tag) doesn't work against
externals.
On Wed, Feb 20, 2013 at 11:42 AM, Geoff Hoffman
wrote:
> Externals are separate repositories by design. You should reference
> externals to a
On Wed, Feb 20, 2013 at 11:52 AM, Bob Archer wrote:
> Some clients like TortoiseSVN have a feature that will pin the external to
> the revision you are copping when doing the tag. Otherwise, you have to do
> it manually before or after you create your tag.
Neither choice 'feels' quite right to m
On Wed, Feb 20, 2013 at 11:58 AM, C M wrote:
> The external definitions do specify a revision. That part is working fine.
>
> I am just not clear on why a simple copy (tag) doesn't work against
> externals.
What do you mean by 'doesn't work'? The copy should have the same
externals as the sourc
>
> > Dear all,
> >
> > I am not sure if this is a bug or I am missing something. But I just
> found a very
> > unusual situation.
> > Please refer to the screenshot below:
> >
> >
> >
> > Both parts in the above screenshot refer to the same revision in the same
> > repository.
> > The first part f
> > Dear all,
> >
> > I am not sure if this is a bug or I am missing something. But I just
> > found a very unusual situation.
> > Please refer to the screenshot below:
> >
> >
> >
> > Both parts in the above screenshot refer to the same revision in the
> > same repository.
> > The first part from
On Wed, Feb 20, 2013 at 12:45 PM, Dr. Leonard Jowers wrote:
>
> ** **
>
> In file
>
>
> 'D:\Development\SVN\Releases\TortoiseSVN-1.7.7\ext\subversion\subversion\libsvn_delta\text_delta.c'
>
>
> line 728: assertion failed (window->sview_len == 0 ||
> (window->sview_offset >=
>
> ab->sb
I am not seeing anything in: /tags/Rel_1.0.
Mind you I am using the Tortoise SVN 1.7 client to do the copy.
On Wed, Feb 20, 2013 at 12:05 PM, Les Mikesell wrote:
> On Wed, Feb 20, 2013 at 11:58 AM, C M wrote:
> > The external definitions do specify a revision. That part is working
> fine.
> >
>
On Wed, Feb 20, 2013 at 12:30 PM, C M wrote:
> I am not seeing anything in: /tags/Rel_1.0.
>
> Mind you I am using the Tortoise SVN 1.7 client to do the copy.
Subversion commands don't recurse into the stuff pulled in with
externals, if that is what you are expecting. But if the thing you
tag h
Bob Archer wrote on Wed, Feb 20, 2013 at 18:23:03 +:
> > > Dear all,
> > >
> > > I am not sure if this is a bug or I am missing something. But I just
> > > found a very unusual situation.
> > > Please refer to the screenshot below:
> > >
> > >
> > >
> > > Both parts in the above screenshot refe
21 matches
Mail list logo
