Rich Freeman on 20 Dec 2018 17:45:46 -0800 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
Re: [PLUG] Git: net time gain or loss? |
On Thu, Dec 20, 2018 at 8:22 PM JP Vossen <jp@jpsdomain.org> wrote: > > I really, REALLY hate the digest thing! You can't tell by looking at > two of them which is old and which is new, and THAT leads to all kinds > of contortions in the interface to hack-around that problem. > So, this gets to the whole "odd workflow" thing but a big concept behind distributed VCS is that there is no one universal version of which commit came first. Granted, in any particular branch there is a sequence. One issue with the design of git is that it isn't clear to me where you'd even store the sequence number and the rules you'd use to determine it. Suppose commit A which has sequence 1 ends up in two branches. They each have a sequence of commits. Then somebody merges one of the commits from one branch into the other, and vice-versa. Merge commits have multiple parents, each with a potentially different sequence number - which number wins? On a side note the physical scientist part of me wants to point out that two observers can't even necessarily agree on the order in which two events even happened in the first place, no matter how accurate their clocks are... :) Git breaks a lot of assumptions people have about how VCS works. Whether that is a good or bad thing depends on perspective, but to truly master it you must bend yourself to the tool. I'll concede that if you're not dealing with world-class programmers that may not be practical. -- Rich ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug