VNC patch for Xserver 1.3

[Alan Hourihane]

On Mon, 2007-08-20 at 10:57 +0100, Colin Guthrie wrote:
> Alan Hourihane wrote:
> > On Mon, 2007-08-20 at 10:19 +0100, Colin Guthrie wrote:
> >> Alan Hourihane wrote:
> >>> It contains a full copy of the xserver tree because it needs to build
> >>> Xvnc. It contains a pre-1.3 copy of the xserver tree though. But it
> >>> wasn't that far behind.
> >> So really, when you say it compiles fine "against" 1.3, you really mean,
> >> it will compile fine and run with 1.3?
> > 
> > Both. I'm just about to merge the 1.3 stable code into xf4vnc anyway.
> 
> Oh great :) So I should be able to generate a patch for Xserver 1.3
> after you've finished that merge? A few strategically placed -j options
> to cvs diff should suffice if I remember my CVS syntax :)
> 
> Thanks for that :D

Actually, I've decided to pull in the current trunk for now. Given that
1.4 is just around the corner.

> >> Do you have any plans on creating a git repo for this stuff? Seems to me
> >> it would make for easier management than CVS (I'm a convert to the
> >> principles of git even if I've still managed to avoid working out how to
> >> build the use the damn thing!!).
> > 
> > Not really. The amount of work going on with the current code really
> > doesn't worry me to move it to git.
> 
> Yes understood.
> 
> FWIW some distros do work on patching X etc. and supply upstream
> patches. Quite often they do this via the creation of their own git
> repository and clone the upstream one.
> 
> If the vnc stuff were in a git repo it would be useful to distros when
> they create their patches to be able to clone it into their own repos
> along with the other patches. So if you feel motivated some people may
> like you for it (me, I really need to learn git properly at some point
> rather than the pathetic clone+pull capabilities I struggle on with ;))

CVS to git and back to CVS isn't hard.

Alan.