[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Issue 1408] - cvs2svn.py error: No origin records for branch 'avendor'.

From: Florian Schulze <florian.proff.schulze_at_gmx.net>
Date: 2003-07-12 10:10:04 CEST

Ok, this seems to be the problem, but how do I fix it? Are there any tools
to fix such things in cvs repositories? If not maybe an option to ignore
certain tags or branches would be nice. In this case I would ignore
"avendor" I guess.

I still don't know how to edit an (my own) issue, and yes I'm logged in and
tried with Opera (7.11) and Internet Explorer (6.0), either I'm just
overlooking something or I can't for some reason.

Florian

On 12 Jul 2003 03:25:10 -0000, <issues@subversion.tigris.org> wrote:

> http://subversion.tigris.org/issues/show_bug.cgi?id=1408
>
> kfogel@tigris.org changed:
>
> What |Old Value |New Value
> ================================================================================
>
>
> Status|NEW |RESOLVED
> --------------------------------------------------------------------------
>
>
> ------
> Resolution| |INVALID
> --------------------------------------------------------------------------
>
>
> ------
>
>
>
> ------- Additional Comments From kfogel@tigris.org 2003-07-11 20:25 PDT -
>
>
> ------
> I believe it is an error for an ,v file to have different names for
> the same branch (whether regular branch or vendor branch doesn't
> matter). That's what's going on here -- branch 1.1.1 has two names,
> 'vendor' and 'avendor', in some of the ,v files in this repository.
>
> I've added a regression test for this in revision 6454.
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Jul 12 10:10:49 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.