On September 27, 2002 11:48 pm, Dan Kegel wrote:
I'm also somewhat opposed to CVS. The big problem with CVS is
that it makes it *too* easy to contribute changes, and too
hard to disentangle changes later when trying to contribute
them back to the main tree. (This kind of thing has caused
I've strongly opposed to using ClearCase for Wine development :-)
I'm also somewhat opposed to CVS. The big problem with CVS is
that it makes it *too* easy to contribute changes, and too
hard to disentangle changes later when trying to contribute
them back to the main tree. (This kind of thing
Am Mit, 2002-09-25 um 23.28 schrieb Lionel Ulmer:
Well, the problem is that I am spoiled by using ClearCase at work (it's
pretty slow sometimes, but well, it's really powerful to manage parallel
developments, something that would be equivalent to what I propose here).
Here you have a good
Am Mit, 2002-09-25 um 23.35 schrieb Lionel Ulmer:
That would be the best... But well, I never heard much good about CVS's
prowess in handling branching (with all the mess like handling properly
conflicts, precise branch management, ...).
I have never understood why people keep saying CVS
I don't get it either.
Synch the current WINE CVS on sourceforge with the winehq one. Create a
branch on the SF CVS. Every so often, create a hook that will commit
changes to the main WINEHQ cvs to the main SF CVS (or create an
automatic hook reading from wine-cvs).
Every so often, someone
Some systems may be better than CVS at this, admitted.
But as long as there are only a few branches and people keep their stuff
more or less in sync with main, I think it'd be fine - especially for
people working on relatively separate subtrees like D3D8.
just to react on Alexandre flame war
Hi all,
As Dimi is not the only one that can start flames on wine-devel, let's start
a new one :-)
When I see the work that is starting to go on on D3D8 or even on my old D3D
code, I think that it would be nice if there was some CVS 'sandbox' where
Wine developper could interact on shared code
As Dimi is not the only one that can start flames on
wine-devel, let's start
a new one :-)
Unfortunately your topic is not controversial enough. :-)
When I see the work that is starting to go on on D3D8 or even
on my old D3D
code, I think that it would be nice if there was some CVS
Unfortunately your topic is not controversial enough. :-)
Damn :-)
Obviously anybody that have the resources can setup a CVS
server and give accounts to others.
Yeah, my plan was to find time and install a CVS server on my own box.
The problem is that 1) I do not have a lot of uplink
Le mer 25/09/2002 à 17:00, Lionel Ulmer a écrit :
Unfortunately your topic is not controversial enough. :-)
Damn :-)
Next time, add something about an automatic indentation program, or
which text editor should be mandatory to hack on Wine. That'll do the
trick :)
Obviously anybody that
On Wed, Sep 25, 2002 at 10:14:26PM +0200, Lionel Ulmer wrote:
This sandbox would be closed (ie it would be a developper only Wine tree) to
NOT start another Wine fork and all development on this sandbox would be
merged back in Wine when they are ready (and then would still go the
Alexandre
On September 25, 2002 05:00 pm, Lionel Ulmer wrote:
Yes, but I do not know if they provide restricted CVS access.
I think it's a great idea, even if for the fact that this way
the changes I make are not sitting on my HD, without backup.
Plus, this way, I can commit _small_ changes in CVS, as I
Next time, add something about an automatic indentation program, or
which text editor should be mandatory to hack on Wine. That'll do the
trick :)
Ah yes... TAB sucks, four spaces rules ! (is it OK for a flame ?)
If you hate it, why do you want to use it then? :-)
Well, the problem is that
IMHO it should be open and be jsut another branch of winehq.
That would be the best... But well, I never heard much good about CVS's
prowess in handling branching (with all the mess like handling properly
conflicts, precise branch management, ...).
Lionel
--
14 matches
Mail list logo
