From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Marcus Better <marcus@better.se>
Cc: git@vger.kernel.org
Subject: Re: [EGIT] assertion failure when renaming file
Date: Tue, 17 Mar 2009 19:40:21 +0100 [thread overview]
Message-ID: <200903171940.21617.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <gpnrcv$mla$1@ger.gmane.org>
tisdag 17 mars 2009 10:43:52 skrev Marcus Better <marcus@better.se>:
> Hi,
Hej,
> I get this assertion failure from the Eclipse plugin 0.4.0.200903110025 whenever I try to rename an untracked file in Eclipse:
There are some ways of corrupting a repo, i.e. the association between the Git provider and the project that results in wierd
behaviours. The ones I know of are related to renaming and moving projects tracked by EGit, which works minus-well.
Could you try with a fresh workspace (you can keep the workdir as-is)?
-- robin
next prev parent reply other threads:[~2009-03-17 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 9:43 [EGIT] assertion failure when renaming file Marcus Better
2009-03-17 18:40 ` Robin Rosenberg [this message]
2009-03-19 19:45 ` Marcus Better
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=200903171940.21617.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=marcus@better.se \
/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).