X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Virus-Scanned: amavisd-new at neurotica.com Message-ID: <508B3FEE.8000200@neurotica.com> Date: Fri, 26 Oct 2012 21:59:10 -0400 From: Dave McGuire User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] The state of gEDA/gaf References: <50892DC8 DOT 6080308 AT laserlinc DOT com> <201210251629 DOT q9PGTfes029100 AT envy DOT delorie DOT com> <50897B77 DOT 1030401 AT laserlinc DOT com> <201210251859 DOT q9PIxw7n004895 AT envy DOT delorie DOT com> <90F80A7D-69D4-408D-AD92-1530A48DFB9E AT noqsi DOT com> <508AC939 DOT 2050205 AT neurotica DOT com> In-Reply-To: X-Enigmail-Version: 1.4.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com On 10/26/2012 02:39 PM, Svenn Are Bjerkem wrote: >> I'm fighting with this exact problem right now. From SCCS, to RCS, to >> CVS, to SVN...and I'm very happy with SVN, but four other developers at >> work are GIT fanatics, so I lost the vote. > > git-svn can be the glue that keeps divided minds together. I am in the > oposite position: Company standard is subversion and no discussion. > Putting git on top of subversion is probably the best way to integrate > the two worlds in a corporate environment. A nice clean mainline in > subversion and all experiments distributed, but under version control > in case you quickly have to stash away the current feature to switch > to a bugfix. Well I don't need to integrate them; I use SVN at home (for work projects as well as personal ones), but we're moving to a more centralized development environment, for at least source code management stuff. Thing is, I don't want to mess with lots of different tools, so in moving to git at work, I will probably end up converting to git on my home network as well. (that's what pushed me to SVN from CVS! ;)) >> At least I won the battle about the use of GIThub...all it took was an >> explanation of what putting the company's extremely proprietary source >> code and protocol implementations "in the cloud" actually MEANT, and >> that discussion was over...we'll have an in-house GIT server soon. ;) I >> wish I'd had a camera handy to capture the looks of abject terror. > > Gitlab in-house is what we use after a while with plain git repository. Oh, that looks nice! And there was just a new release a couple of days ago. ;) Thank you for the suggestion; I will likely go that route when it comes time for me to set up the server for work. -Dave -- Dave McGuire, AK4HZ New Kensington, PA