X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Wed, 18 Mar 2015 12:46:35 -0400
Message-Id: <201503181646.t2IGkZ0w013928@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <AC2776EE-AD74-4AC9-BCB1-9F40CC439B5D@noqsi.com> (message from
	John Doty on Wed, 18 Mar 2015 10:40:09 -0600)
Subject: Re: [geda-user] pcb alternatives
References: <CAHLh21Cdm=YZuqCQ+gCHSviJquahr6cnAQ-VBLR4BSs-nfHOig AT mail DOT gmail DOT com> <CAOFvGD4+4bHXNYLvePi70wb_1A4=dQgb_Ov3xBghoKbXQUsSGA AT mail DOT gmail DOT com> <5508413E DOT 4000405 AT ecosensory DOT com> <46050a0c DOT 619 DOT 14c2850d052 DOT Webtop DOT 45 AT optonline DOT net> <CAGYR9veihi_M+B0HXptGYQLMO8=B_KOLM2wmrRNkMLG_9MdQrA AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1503180357520 DOT 25799 AT igor2priv> <CAGYR9ve_n7VmZ8x-jCQK5eKHMNGp6an9o8EwYZnWQWFiCpGnXg AT mail DOT gmail DOT com> <alpine DOT DEB DOT 2 DOT 00 DOT 1503180827170 DOT 25799 AT igor2priv> <CAC4O8c--CeEiKjxCKrs38XGjOyPS0Cy6scZ5HsAFgpi5xDpP_w AT mail DOT gmail DOT com> <201503181619 DOT t2IGJkZD012945 AT envy DOT delorie DOT com> <AC2776EE-AD74-4AC9-BCB1-9F40CC439B5D AT noqsi DOT 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
Precedence: bulk


> Well, of course, that's a matter of trying to do manually what git
> does automatically. The commit messages are your changelog in git.

Designing a workflow around what your CMS requires is an example of
the tail wagging the dog.  Yet, pcb's Changelog is generated from the
git commit logs, so I understand your specific comment.  But my
example was one of "the project I work on has a workflow incompatible
with git's desires" - *any* case where a project has a file that's
commonly changed, and thus commonly conflicted, it going to suffer
from git's workflow.