Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 345321

Summary:	Problems with cloned read-only Git repositories
Product:	[ECD] Orion	Reporter:	Boris Bokowski <bokowski>
Component:	Client	Assignee:	Malgorzata Janczarska <malgorzata.tomczyk>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	Szymon.Brandys
Version:	0.2
Target Milestone:	0.2
Hardware:	PC
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Boris Bokowski

2011-05-10 15:04:08 EDT

Clone from the following URL: https://bokowski@github.com/bokowski/jsconf-2011.git and then make local changes. Go to the git-status page, stage your changes, commit. You get an error message. Trying to unstage your change also leads to an error. Not even sure if Git log works. This case seems to need some testing...

Comment 1 Malgorzata Janczarska

2011-05-11 09:54:41 EDT

Boris, I tried to reproduce the problem base on your scenario and I found Bug 345416, Bug 345420 and Bug 345422, but none of they really matches problem described by you. I tried your repo and other read-only repos, but I suppose problem desn't have much to do with the repo being read-only.
Could you:
1. Update your jgit
2. Pull latest changes from git
3. Try to reproduce
and update the bug with some more details: error message you wrote about, stack trace if any.

Comment 2 Malgorzata Janczarska

2011-05-26 04:22:29 EDT

Boris, do you still have problems with cloning repositories?

Comment 3 Boris Bokowski

2011-05-26 19:20:45 EDT

(In reply to comment #2)
> Boris, do you still have problems with cloning repositories?

No, I haven't seen this problem since. Thanks for fixing (or updating to a fixed JGit)!

Comment 4 Malgorzata Janczarska

2011-05-27 05:01:24 EDT

(In reply to comment #3)
> No, I haven't seen this problem since. Thanks for fixing (or updating to a fixed
> JGit)!
So I'm marking fixed.