Version control

On 6/28/2010 8:17 PM, David Ingebretsen wrote:

I am a one man shop, nonetheless, I find I need to establish some kind of

revision control. I'm struggling trying to find the best way in Eagle to

keep track of notes, changes, etc.

1. I'd like to have a way to automatically/easily bump the revision of a

schematic/PCB. Something like version control in software design.

2. I'd like a straightforward way to track the changes and keep notes and

comments. It's a pain to add text one line at a time on the schematic

itself and I find the supplied "frames" to be a bit cumbersome to use.

>

I've struck out trying to find anything in the user manual or in the list.

>

>

I've looked through the download section for ULPs, but didn't find

anything.

>

I find I'm already getting lost in revisions.

>

Thanks for any advice.

After suffering CVS and SVN for many years, I finally followed Linus to

GIT and have seen the light.  GIT does version control like a normal

human would expect.  We've changed hundreds of projects over to it so

far.  GIT does for versioning control software what Linux did for UNIX, IMO.

MB: Can you be specific? How is git better than svn? I've considered changing over but haven't seen a convincing argument.

--Randy

Randy Yates <yates@ieee.org> wrote:

MB: Can you be specific? How is git better than svn? I've considered

changing over but haven't seen a convincing argument.

Consider GIT as an distributed SVN. All data is local, while with SVN much

data is on the server. If for some reason the server is unaccessible, SVN is

hampered much more than GIT.

--

Uwe Bonnes                bon@elektron.ikp.physik.tu-darmstadt.de

Institut fuer Kernphysik  Schlossgartenstrasse 9  64289 Darmstadt

-

Tel. 06151 162516 -

Fax. 06151 164321 -

Uwe Bonnes wrote:

>Randy Yates <yates@ieee.org> wrote:

>> MB: Can you be specific? How is git better than svn? I've considered

>> changing over but haven't seen a convincing argument.

>Consider GIT as an distributed SVN. All data is local, while with SVN much

... and therefore DRCS usually have better merge handling (because it

heavily depends on it).

For the Eagle users this doesn't make much difference, since files are

binary and even with the upcoming text format, I don't expect we can

merge concurrent changes in Eagle brd/sch. Maybe in libraries...

BTW: If someone is interested in DRCS, and can't rule out using

Windows, he should look also at Mercurial as an alternative to Git.

Git developers don't like Windows, and they don't like Windows users.

Oliver

Uwe Bonnes wrote:

>Randy Yates <yates@ieee.org> wrote:

>> MB: Can you be specific? How is git better than svn? I've considered

>> changing over but haven't seen a convincing argument.

>Consider GIT as an distributed SVN. All data is local, while with SVN much

... and therefore DRCS usually have better merge handling (because it

heavily depends on it).

For the Eagle users this doesn't make much difference, since files are

binary and even with the upcoming text format, I don't expect we can

merge concurrent changes in Eagle brd/sch. Maybe in libraries...

BTW: If someone is interested in DRCS, and can't rule out using

Windows, he should look also at Mercurial as an alternative to Git.

Git developers don't like Windows, and they don't like Windows users.

Oliver