Re: [B2-devel] Various issues SheepShaver OSX

[Ronald P. R. <ron...@xs...>]

Thanks for your answer. But remember that I am only a (experienced) user of SheepShaver and BasiliskII, not a developer. I filed issues I encountered as a user with builds created with recent source. I do not intend to change anything myself, I would not know how to, I hope others will solve the problems.

"Clone repository"? "Working directory"? What is my working directory? Do I have one?

I only want to be able to download the source of certain dates, to build the application from it, so I can see and report when a problem starts. That could provide information about where to look for the code that is responsible.

With CVS I knew the commands needed to do that, and I did so on several occasions. But I do not know how to do that with GitHub. Your instructions presuppose knowledge I do not have and possibly need software on my Mac I do not have installed. So far, I only accessed cebix/macemu with a web-browser and there I see only one link to download the latest revision as zip archive. I don't think I want or need the whole repository and history.

Best,  Ronald.


Op 28 jun. 2012, om 20:09 heeft Giulio Paci het volgende geschreven:

> On 28/06/2012 19:13, Ronald P. Regensburg wrote:
>> 
>> I started to file issues with SheepShaver OSX here:
>> 
>> https://github.com/cebix/macemu/issues
>> 
>> I hope someone will look into these issues. More will follow.
>> 
>> An important issue is that SheepShaver OSX appears to have lost the ability to mount CD-ROMs sometime in the past few months. I have no experience with GitHub and I do not know how to narrow the issue down to a specific patch. With CVS I used to download the source from different dates to see where a specific issue appeared. Can that be done here as well? How?
> 
> 1) When you clone a repository (e.g., git clone
> https://github.com/cebix/macemu.git) you have the whole history in the
> .git directory in your working directory.
> 
> You can get a specific revision with the checkout command (e.g.: git
> checkout <hash_tag_of_the_revision>). This will change the content of
> your working directory with those of the desired revision.
> 
> You can get the revisions history (with hash tags) with the log command.
> You can see which files have been changed with "git log --raw".
> 
> You can also compare directly two revisions with the diff command.
> 
> You can also have a look at the bisect command.
> 
> Remember that you also can do "git help command" to get help.
> 
> 2) If you want to change something and not just find the revision that
> introduced the bug, I suggest to use the fork button on github and clone
> your repository instead of the main one. This will simplify merging your
> changes in the main repository later.
> 
> Bests,
> 	Giulio.