Hi Gregg,
The transition (cvs->git) was recent (a couple of weeks). The biggest
barrier was teaching an old dog (me) new tricks.
You are right, there are many source management systems available, but it
adds complexity to use them simultaneously.
cvs was working fine, and I had some nice reporting tools that I haven't
been able to replicate. However, git seems to have a number of advantages:
1. renaming and reorganizing files doesn't lose all history.
2. it's easier to modify a version, experiment, and then submit the changes
back.
3. New developers are more used to git, have the tools and workflow already
at hand, and thus can participate more easily.
Although OWFS is stable, functional, and active, I'm currently the only one
committing code. I wondered if the development model was partly to blame,
and so decided to modernize the tools.
If I could only do something about autotools...
Paul
On Tue, Apr 29, 2014 at 8:47 PM, Gregg Levine <gregg.drw...@gmail.com>wrote:
> Hello!
> SF delivers both Git and CVS and probably SVN (still) and probably any
> others we can dream up. So when was CVS depreciated? I believe I
> managed to update the CVS one last night, and even tried to build the
> P3 release of 2.9 on my Slackware 13.37 system. (Currently the only
> one running.) It complained about libtool errors as related to age and
> so forth, it even insisted that I obtain a new release of such from an
> Ubuntu system.
>
> Paul is that where the original code is being built? (I'm on Slackware.)
> -----
> Gregg C Levine gregg.drw...@gmail.com
> "This signature fought the Time Wars, time and again."
>
>
> On Tue, Apr 29, 2014 at 8:35 PM, Paul Alfille <paul.alfi...@gmail.com>
> wrote:
> > Release Notes owfs 2.9p4
> > 4/30/2014
> >
> > New features
> > 1. Switch to git for source management
> > Still hosted on sourceforge.net
> > git clone git://git.code.sf.net/p/owfs/code owfs-code
> > cvs history brought over.
> > 2. Clean and test DS2409 (Microlan) hubs
> > Addressing problem found by Ors Tiszay
> > Works well with passive devices
> > Problems with powered slaves, but probably not a software issue.
> > 3. Improved and tested owserver protocol for server-to-server
> communication
> > Use md5 hash for unique token
> > Fixed byte counting issue in write messages
> > Null-terminated string no longer required in path string
> > (problem pointed out by Stefano Miccoli)
> > 4. Added /system/configuration/version
> > Reports owserver version
> > Request from Stefano Miccoli
> >
> > Fixes
> > 1. Double initialization of mutex fixed
> > Show stopper in FreeBSD
> > Found by Johan Strom
> >
>
>
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos. Get
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Owfs-developers mailing list
> Owfs-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/owfs-developers
>
------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos. Get
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Owfs-developers mailing list
Owfs-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/owfs-developers
