On 5/28/07, Bryan DeGrendel <[EMAIL PROTECTED]> wrote:
I believe most non-bug fix changes will be limited to a small part of the
WINE tree (the mscoree dll), so creating an entire git fork is overkill for
On the contrary, I believe that git is ideal for forking (and later
merging) like this.
On 5/28/07, Maarten Lankhorst <[EMAIL PROTECTED]> wrote:
John Klehm schreef:
> Hey Maarten and all,
>
> Good idea about publishing the changes. I was thinking to use
> Google's project hosting thing for mine I think it supports SVN or
> something though. Guess I can try and figure out a git fe
John Klehm schreef:
> Hey Maarten and all,
>
> Good idea about publishing the changes. I was thinking to use
> Google's project hosting thing for mine I think it supports SVN or
> something though. Guess I can try and figure out a git feed on a
> different server too, we'll see.
Git is the reposi
Hey Maarten and all,
Good idea about publishing the changes. I was thinking to use Google's
project hosting thing for mine I think it supports SVN or something though.
Guess I can try and figure out a git feed on a different server too, we'll
see.
Just want to say hello and good luck. I'm glad
For all other students joining SummerOfCode, I think it's a good idea if
we have a public place where we can see each other's changes.
I set up my own fork, sound.git at http://repo.or.cz/w/wine.git - if
others want to do the same I encourage them to do so, it's easy when you
figure out how to git
