git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Vilz <niv@iaglans.de>
To: Eric Wong <normalperson@yhbt.net>
Cc: git@vger.kernel.org
Subject: Re: git-svn throwing assertion on old svn tracking branch
Date: Fri, 22 Dec 2006 03:16:13 +0100	[thread overview]
Message-ID: <20061222021613.GB9595@hermes> (raw)
In-Reply-To: <20061222013510.GA9595@hermes>

On Fri, Dec 22, 2006 at 02:35:10AM +0100, Nicolas Vilz wrote:
> On Wed, Dec 20, 2006 at 05:05:20PM -0800, Eric Wong wrote:
> > Nicolas Vilz <niv@iaglans.de> wrote:
[...]
> 
> The repository i am tracking does still exist. both, the tree and the
> repository are on the same revision-number, so i am a bit clueless.
> 
> I tried a fresh fetch of this repository, it worked. so it shouldn't be
> a client-server version mismatch..
> 
> I also tried 
> 
> rm -rf .git/svn/svn_master/tree && git-svn rebuild -i svn_master
> 
> this had no effect to git-svn fetch -i svn_master... i get the very same
> error message...
> 
> I didn't alter there anything, so i think, fetching works, but if
> nothing is there to fetch, there is the initial error message...
> 
> beneath there is svn, version 1.4.2 (r22196) ... on that repository is
> Subversion version 1.1.4 (r13838).

i should ammend, that the same error message comes, when i want to
dcommit something in this repository...

  reply	other threads:[~2006-12-22  2:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-20 23:55 git-svn throwing assertion on old svn tracking branch Nicolas Vilz
2006-12-21  1:05 ` Eric Wong
2006-12-22  1:35   ` Nicolas Vilz
2006-12-22  2:16     ` Nicolas Vilz [this message]
2006-12-22  8:38       ` Eric Wong
2006-12-22  9:43         ` Nicolas Vilz
2006-12-23  6:45           ` Eric Wong
2007-01-01  2:27   ` Eric Wong
2007-01-05  9:18     ` Nicolas Vilz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061222021613.GB9595@hermes \
    --to=niv@iaglans.de \
    --cc=git@vger.kernel.org \
    --cc=normalperson@yhbt.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).