Paris Metro lines on a Git graph

nothrabannosir wrote: post #3

tbronchain wrote: post #2

42 commits. Well done :)

On master.. There are 300 stops, so you'll need at least that many commits. There's different branches for different lines.

Shouldn't that be "maître"? ;)

Re: Paris Metro lines on a Git graph

#6

Post by christianmann » Sun, Jun 07, 2015, 2:05 PM UTC

Similar idea for DC Metro here: https://github.com/bburky/git-dc-metro

Re: Paris Metro lines on a Git graph

#7

Post by aout » Sun, Jun 07, 2015, 2:42 PM UTC

pudo wrote: post #5

nothrabannosir wrote: post #3

Earlier quoted context omitted.

On master.. There are 300 stops, so you'll need at least that many commits. There's different branches for different lines.

Shouldn't that be "maître"? ;)

You can be sure it's not Imperial

Re: Paris Metro lines on a Git graph

#8

Post by stinky613 » Sun, Jun 07, 2015, 2:49 PM UTC

This is pretty cool. Does anyone think this would work well for some network topology mapping?

Re: Paris Metro lines on a Git graph

#9

Post by a3n » Sun, Jun 07, 2015, 3:45 PM UTC

> I had to remove some interconnections, because there were some cycles.

Because git doesn't allow cycles? Then as cool as this is (and it's very cool), perhaps this isn't an appropriate tool for this purpose.

Or might the natural, human-built cycles be expressable as subrepositories?

Re: Paris Metro lines on a Git graph

#10

Post by scrollaway » Sun, Jun 07, 2015, 3:48 PM UTC

a3n wrote: post #9

> I had to remove some interconnections, because there were some cycles. Because git doesn't allow cycles? Then as cool as this is (and it's very cool), perhaps this isn't an appropriate tool for this purpose. Or might the natural, human-built cycles be expressable as subrepositories?

> perhaps this isn't an appropriate tool for this purpose

Would Mercurial be more appropriate, or do you think DVCS are simply not an ideal way of mapping metro lines?