Detlef Riekenberg wrote:
When switching the Instructions for the Wine tree from cvs to git, the Instructions for the additional modules (docs, lostwages, ...) got lost.
They're still available at the old link:
http://www.winehq.org/site/cvs
It would be nice to move the remaining modules to Git too, IMO.
Mike
On 9/27/06, Mike McCormack mike@codeweavers.com wrote:
It would be nice to move the remaining modules to Git too, IMO.
And you can do all future web site matince IMO!
Tom
Mike
On Do, 2006-09-28 at 05:31 +0900, Mike McCormack wrote:
When switching the Instructions for the Wine tree from cvs to git, the Instructions for the additional modules (docs, lostwages, ...) got lost.
They're still available at the old link:
I was unable to find a Link on the Frontpage, but since git is prefered over CVS, adding cvs next to git might be not the best Idea. The downside is, that the Patch double the information (as already done with the LRX-Tree).
Today, I found a Link to the cvs-Page: The Release-Announce.
It would be nice to move the remaining modules to Git too, IMO.
You are welcome to send a Patch.
OTOH, is a change to git for all modules really needed?
On Thu, 28 Sep 2006, Mike McCormack wrote: [...]
They're still available at the old link:
Yes, but this makes it harder to find them which is not going to foster activity on the Wine documentation for instance!
It would be nice to move the remaining modules to Git too, IMO.
These modules are hosted on SourceForge so that more people can have commit rights without having to bother Newman every time or reimplementing all the user management on winehq.org. I agree that it would be nice to switch them to Git, but you will have to convince the SourceForge guys first.
-
Detlef Riekenberg -
Francois Gouget -
Mike McCormack -
Tom Wickline