delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to geda-user-bounces using -f |
X-Recipient: | geda-user AT delorie DOT com |
Message-ID: | <20130115203627.19881.qmail@stuge.se> |
Date: | Tue, 15 Jan 2013 21:36:27 +0100 |
From: | Peter Stuge <peter AT stuge DOT se> |
To: | geda-user AT delorie DOT com |
Subject: | Re: [geda-user] geda-skeleton-project: Lowering the cost of a |
starting a gEDA project | |
Mail-Followup-To: | geda-user AT delorie DOT com |
References: | <87wqvhd4tw DOT fsf AT gmail DOT com> <kd21ao$j6j$1 AT ger DOT gmane DOT org> <20130115013756 DOT 9917 DOT qmail AT stuge DOT se> <CAOP4iL0yLZ-gvovCy5zCmJyjOXUUaoOB5U1+6CqcD20BM15FiQ AT mail DOT gmail DOT com> <50F4E4D1 DOT 3010802 AT ecosensory DOT com> <CAOP4iL1f=3TV5UKUjyJtpUw_5oBDxpk=5S2F=dEcUC2UYiNhVQ AT mail DOT gmail DOT com> <878v7uv4gl DOT fsf AT gmail DOT com> <CAOP4iL3fobzQNV5YN7kQ74L2Z2fsz1E3XJDffA1U+jBTF9qjXA AT mail DOT gmail DOT com> |
MIME-Version: | 1.0 |
In-Reply-To: | <CAOP4iL3fobzQNV5YN7kQ74L2Z2fsz1E3XJDffA1U+jBTF9qjXA@mail.gmail.com> |
Reply-To: | geda-user AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | geda-user AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
Ouabache Designworks wrote: > The hardware designer does not know if a verilog .v file was > handcrafted and must be checked in or generated by finiteStateMachine > tool and should not be checked in. Uh? The person who handcrafted the file will surely know that it needs to be committed? > Setting up the ignore and clean functions can be done but will > take a lot of effort. I don't see why? Don't get stuck on the existing user interfaces for these operations, just think of how the operations fit into the workflow. > All VersionControlSystems will do four things: The git data model delivers well on all points. > Beyond that they all provide various features to help developers and > most VCS wars are fought over these features. If you are smart then > you will not use any of them because they will all complicate > things when it comes time to move your data on to the next VCS. I disagree. If a(n open) tool has a useful feature then it's a waste of time not to take advantage of it. You are absolutely right that migration in and out of a given system are critical requirements for longevity. I'm thinking about how well the git data model fits orange. So far it seems really good. //Peter
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |