Thanks, Curt, for forwarding my xas...@xastir.org message to xastir-dev,
which I hardly even think about much, since most of the traffic is on the
user group, not the dev group.
Now that Curt has been very busy updating all the README files to translate
CVS commands and repo URLs to their roughly corresponding git counterparts,
I thought I'd take a moment to point out that our transition to github has
made the process of contributing to the Xastir development a bit simpler than
it used to be, should you choose to take advantage of it.
Git is very different from CVS, because of its distributed model, and it makes
possible a better workflow for managing contributions. Consider this
old-school way for you to add or fix Xastir code under CVS:
0) Notice an issue you'd like to work on
1) Check out the current code from CVS
2) Do code changes
3) Run a CVS diff command, and forward the resulting patch to one of the
folks who have commit access (almost always Curt).
4) Wait for that person to review the code, then commit it.
5) Repeat.
A better approach, using github's "pull request" capability, is now:
0) Notice an issue
1) Fork the Xastir repo on github, creating your own copy to which you
automatically have all admin rights.
1a) Clone your forked copy
2) Create a feature branch in your repo, and make code changes on that branch
3) Push your new feature branch with your code changes to github.
4) Issue a "pull request" to the Xastir project.
This enables some Xastir developer with push access to the project to grab
all of your changes, review them, test them, provide feedback, and ultimately
copy your changes (via a git merge operation) into the main branch of the code
for everyone to enjoy.
One of the benefits of doing it this way is that you actually show up in the
project history as the author of the changes, without one of the developers
having to give you credit by mentioning your name in the commit log, or
adding comments to the code to that effect.
Please see https://help.github.com/articles/using-pull-requests/ for
details on the process. If you think this is something you're likely to do,
then you should definitely read some of the references at the bottom of
README.GIT to help the process go smoothly. These include things like the
complete "Pro Git" book, guidelines for writing good commit messages, and
managing your git repo so that the project history looks nice and clean to
people who are browsing it (via git log, gitk, or other repo browsers).
Share and Enjoy.
On Thu, Jul 07, 2016 at 11:18:59AM -0700, we recorded a bogon-computron
collision of the <curt.w...@gmail.com> flavor, containing:
> ---------- Forwarded message ----------
> From: Tom Russo <ru...@bogodyn.org>
> Date: Thu, Jul 7, 2016 at 9:31 AM
> Subject: [Xastir] Xastir development source now on github, sourceforge CVS
> now closed to new commits.
> To: xas...@xastir.org
>
>
> As announced a couple of months ago, Curt and I have been talking about
> moving
> Xastir version control over to github, and discontinuing use of sourceforge
> and CVS for hosting the main repository.
>
> There wasn't much feedback from the group about that, and yesterday we went
> ahead and did it. The sourceforge CVS repository is still there, but all
> commit access has been locked down and we'll shut down the CVS repo
> altogether
> when we're sure this is all working properly.
>
> We have not yet migrated the issue tracking data from sourceforge to github,
> but that is not a high priority as we have not been using the issue tracker
> much, and most of the issues that are there have been getting ignored for
> years.
>
> We may continue to use Sourceforge for distribution of release tarballs.
> In fact, we will almost certainly continue to use Sourceforge for that.
>
> The Xastir wiki and home page have NOT yet been updated to reflect this
> move of version control. It will be.
>
> In the meantime, if you have been using CVS to keep current with Xastir,
> you'll have to change.
>
> The short story:
>
> To get a copy of the development repository, you must have git installed
> on your system.
>
> To obtain the repo for the first time:
> git clone https://github.com/Xastir/Xastir.git
>
> This will create an Xastir subdirectory, and put a clone of the repository
> into it as well as checking out the "master" branch of the code into that
> working directory.
>
> At this point, your Xastir subdirectory can be used just as you had used
> a cvs checkout to build Xastir.
>
> Periodically, you can update the code by "cd"ing into the repo directory
> and executing:
> git pull
>
>
> If you intend to contribute code to the Xastir project, there's going to be
> more to learn, but if you were just using CVS to get access to the latest
> source, these two commands will be sufficient to get you up to speed, and
> correspond very, very roughly to the "cvs checkout" and "cvs update"
> commands
> you were used to.
>
> A new README.GIT file exists in the source tree, just as there had always
> been a README.CVS.
>
> --
> Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/
> Tijeras, NM QRPL#1592 K2#398 SOC#236
> http://kevan.org/brain.cgi?DDTNM
> echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z]
> [n-z][a-m]
>
>
>
>
> _______________________________________________
> Xastir mailing list
> xas...@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir
>
>
>
> --
> Curt, WE7U
> http://we7u.wetnet.net
> http://www.sarguydigital.com
> _______________________________________________
> Xastir-dev mailing list
> Xastir-dev@lists.xastir.org
> http://xastir.org/mailman/listinfo/xastir-dev
--
Tom Russo KM5VY SAR502 DM64ux http://www.swcp.com/~russo/
Tijeras, NM QRPL#1592 K2#398 SOC#236 http://kevan.org/brain.cgi?DDTNM
echo "prpv_a'rfg_cnf_har_cvcr" | sed -e 's/_/ /g' | tr [a-m][n-z] [n-z][a-m]
_______________________________________________
Xastir-dev mailing list
Xastir-dev@lists.xastir.org
http://xastir.org/mailman/listinfo/xastir-dev
