Re: [B2-devel] Thoughts on SheepShaver and Basilisk II

[Frank T. <fra...@gm...>]

On Fri, Jun 15, 2012 at 12:08 PM, Alexander von Gluck <kal...@un...
> wrote:

> On 15.06.2012 11:13, Diskutant wrote:
> > I'm 100% with Alexander!
> >
> > It's so much easier to use GitHub, I fork projects with a simple click,
> do
> > changes, those are public for everyone and
> > if I think I finished something good I ask the main repo to just pull my
> > changes. I love it!
> > Just because I know how to use CVS doesn't mean I want to. Besides, one
> > would need write access.
> >
> > Alex, I would say just import the CVS code into GitHub or where ever you
> > like, let us know and we just might move
> > over. :-)
>
> Done.
>
> SheepShaver has a new fork called SheepShear.
>
> https://github.com/kallisti5/sheepshear
>
>
> Feel free to utilize any patches in sheepshear into the sheepshaver code.
>
> Right now i'm pouring over the other existing forks on Github of
> SheepShaver
> and cherrypicking patches not in the
> SheepShaver codebase (giving the other authors credit)
>
> I'm going to discontinue this discussion on
> bas...@li... as it is no longer relevant to
> SheepShaver
> or Basilisk II.
>
> I don't know about that. Since both projects seek to do the same things
using the same tools, I think that keeping a shared discussion of common
issues is the best way to advance both projects.


> Thanks for all the hard work over the years!
>
>  -- Alex
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> basilisk-devel mailing list
> bas...@li...
> https://lists.sourceforge.net/lists/listinfo/basilisk-devel
>