[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Speech-dispatcher git repository created.

From: Luke Yelavich
Subject: Speech-dispatcher git repository created.
Date: Fri, 12 Jun 2009 15:12:58 +1000

Hi all
I have imported speech-dispatcher from CVS into a git repository. Jan Buchal 
indicated to me last week that Brailcom were looking into moving to git, and 
due to the work I will be doing on speech-dispatcher in the coming months, I 
thought I'd accelerate this process for speech-dispatcher. Note that due to 
some commits being made with no log messages, there are several commits in the 
git repository that have no log message associated with them.

There was one tag in the original CVS repository, for version 0.6.4. This tag 
was imported successfully, but I have retagged version 0.6.4 with a different 
tag naming scheme. I have also tagged v0.6.7 as well as I can identify in terms 
of commits, so that it will be easier to work out what has been changed since 
the last speech-dispatcher release.

The git repository can be found here: http://git.themuso.com. The page will 
give you a gitweb view/summary of the repository, including the URL needed to 
clone the repository to your machine. If Brailcom wish to move more projects to 
git, and get infrastructure set up, I am happy to help the conversion and setup.

In the meantime, I will be starting my work using this git repository as the 
place I will store my commits. There is currently one extra branch, CVS-Head, 
which shows the current state of the speech-dispatcher code at the time I 
pulled it from CVS. My work will be done in the master branch, and I may create 
other branches as my work progresses.

I was pondering setting up a mailing list for git commits to the 
speech-dispatcher repository, however Brailcom may want me to send these 
commits to one of their own lists, eg the speechd-commits list, depending on 
how soon they want to move the speech-dispatcher repository and other 
repositories over to git.

Finally, with the move to git, it allows anybody to make their own repository 
copy locally, and make changes, and even more importantly, send patches. One of 
git's best features in my opinion, is the ability to generate patches from 
commits, which can then be emailed directly, for applying to another 
repository, with full authorship and date in tact. So if you are following the 
work I am doing, and want to send me a patch, git will make this much easier 
for all of us.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]