On 25 June 2018 at 19:41, Tim Mackinnon <tim@testit.works> wrote:
I���d be really interested if someone with lower level GIT knowledge might try a:

git checkout��<gitid>��src/<proj>/<class>.class.st��

For their project - as I don���t understand what I���m doing wrong - and I���d like the comfort of knowing that our source is in a place/state where we can rely on normal git tools in a case of emergency. At the moment, I���m a bit nervous that we are corrupting something .

Tim

I'm not sure if this is what you wanted, but I found a test case for for Pharo 7, a deleted��class��"MultiByteFileStreamTest.class.st"
https://github.com/pharo-project/pharo/pull/1031/files#diff-750a25fb99d29cda8c2c388dc18f6c1cL1

From Windows 10 cmd.exe I tried the following (I can't remember which tool installed `git`)...

> mkdir C:\temp\test
> cd C:\temp\test
> git clone��git@github.com:pharo-project/pharo.git
> cd pharo\src\Deprecated70
> dir����Multi*
no result
>��git checkout e74308e67d9f84 MultiByteFileStreamTest.class.st
> dir Multi*
MultiByteFileStreamTest.class.st

Then I compared the file I checked out to the raw file on github and they were identical...


btw, I did get a momentary error "error: pathspec 'src/Deprecated70/MultiByteFileStreamTest.class.st' did not match any file(s) known to git."
when I incorrectly did...
>��cd pharo\src\Deprecated70
> git�� git checkout e74308e67d9f84�� src/Deprecated70/MultiByteFileStreamTest.class.st


This worked��with the longer path...��
>��cd pharo
> git����git checkout e74308e67d9f84����src/Deprecated70/MultiByteFileStreamTest.class.st

cheers -ben