X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f X-Recipient: geda-user AT delorie DOT com X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.98.4 at av01.lsn.net Message-ID: <5440A6B2.2000900@ecosensory.com> Date: Fri, 17 Oct 2014 00:18:42 -0500 From: John Griessen User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: geda-user AT delorie DOT com Subject: Re: [geda-user] SchemeIt References: <00E6DEBC-05AB-4079-9E88-152225FF6DDE AT qux DOT com> <87wq80xauh DOT fsf AT hotmail DOT com> <87siinykoy DOT fsf AT hotmail DOT com> In-Reply-To: <87siinykoy.fsf@hotmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Reply-To: geda-user AT delorie DOT com On 10/16/2014 12:43 PM, Enoch wrote: > I believe that Geda should start > adding tags to the sch and pcb which are related to version control. > > In short, add revision control support within gschem, within pcb, etc. We have attributes. All that is needed for a VCS merge to work easily is same handling of white space in file structure no matter how or in what order a drawing is created. Possibly another external tool could alphabetize the lines in a .sch or .pcb file so each collaborator would have merges go in the same spot in the files... or possibly that "alphabetic sorting" of lines of a .sch or .pcb file could be done internally. I don't see any need or anyone with time to spend on reinventing a VCS within PCB or gschem, just use one externally on the data.