This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: xwinclip/-clipboard - Development on no selection stealing version
- From: David Fraser <davidf at sjsoft dot com>
- To: cygwin-xfree at cygwin dot com
- Date: Sat, 07 Jun 2003 16:26:59 +0200
- Subject: Re: xwinclip/-clipboard - Development on no selection stealing version
- References: <3EE0DB9A.4070508@msu.edu>
- Reply-to: cygwin-xfree at cygwin dot com
Harold L Hunt II wrote:
I have been working with the code for Keith Packard's XFIXES
extension. The XFIXES extension includes a new hook in
Xserver/dix/dispatch.c that allows functions within the Xserver (such
as the XFIXES xtension) to register for a callback when a selection's
ownership changes, among other things.
[snip]
2) What would be the best way for me to share the code with other
developers? I don't want to commit the XFIXES stuff to our
SourceForge tree's HEAD, but could I use another branch? If so,
please give me some instructions for what to do... I haven't got time
to study CVS all day.
Basically just say cvs tag -b XFIFES_BRANCH on a tree you've checked out
(so far unchanged). Then say cvs update -r XFIFES_BRANCH so that it
marks the code as using that branch (for future commits). Then do all
the changes (you could do this by making a diff from your existing work
and use patch to apply it to this tree), and commits will go onto the
branch. Others can get them by doing cvs update -r XFIFES_BRANCH.
From the cvs man page:
Say you have been working on some extremely experimental software, based
on whatever revision you happened to checkout last week. If others in
your group would like to work on this software with you, but without
disturbing main-line development, you could commit your change to a new
branch. Others can then checkout your experimental stuff and utilize
the full benefit of cvs conflict resolution. The scenario might look like:
example% cvs tag -b EXPR1
example% cvs update -rEXPR1
[[ hack away ]]
example% cvs commit
Others would simply do `cvs checkout -rEXPR1 whatever_module' to work
with you on the experimental change.
Hope that helps
David