TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Version Control Beyond Git

5 pointsby oneofthose12 months ago

5 comments

NikkiA12 months ago
Most of these are <i>owned</i> by some megacorp, which IMO renders them untrustable, the same may have been true for git at a time (I can&#x27;t remember if Linus still &quot;worked for&quot; redhat at the time of git&#x27;s creation), but it&#x27;s sufficiently insulated from that now - even if MS is viewed as holding github&#x27;s reins too closely. But I&#x27;m not trustly a VCS from facebook, or even google.<p>The real issue is though, that each time someone writes a new VCS they seem to want to make it centralised again, often with silly ideas like auto-uploading changes. I do dislike the git stash and the &quot;mess&quot; of untracked files in git status, but I&#x27;m not sure what the true answer is.
kevincox12 months ago
The feature I think I would most like to see is support for patches as a more first-class object. For example reverts and cherry picks have no real metadata. This leads to conflicts when merging branches that have cherry picks (although they often auto-resolve if they are exactly the same diff) and makes asking &quot;Does $branch contain $patch&quot; basically impossible to answer.<p><a href="https:&#x2F;&#x2F;pijul.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;pijul.org&#x2F;</a> greatly improves this by making patches a first class object (and commits are basically sets of patches). I think it has some great ideas to improve the really gnarly parts of Git low-level behaviour. (Not just surface-level UI issues)
评论 #40453166 未加载
brylie12 months ago
&gt; Mercurial was started almost at the same time as Git by Olivia Mackall, a kernel hacker at the time, motivated, just like Linus, by the BitKeeper and SourcePuller drama of spring 2005.<p>Perhaps ironically, the now open-source BitKeeper may meet many of the author’s criteria for a post-Git version control system, at least at first glance from the BitKeeper homepage.<p><a href="https:&#x2F;&#x2F;www.bitkeeper.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.bitkeeper.org&#x2F;</a>
评论 #40453196 未加载
jmclnx12 months ago
I think git is OK, but one item I miss is what CVS&#x2F;RCS has, &quot;$Id$&quot;. It is very difficult to see the version of a binary if its source is tracked in git.<p>Yes, someone said there is a way to get a git tag in the source, but the tag is not as easy to view as &quot;$Id$&quot; thus it is not obvious if it is the latest version.<p>But, curious he did not mention CVS and RCS :)
评论 #40453246 未加载
评论 #40468702 未加载
评论 #40443632 未加载
brylie12 months ago
What would be your top choice for a post-Git VCS and why? I’m interested to try alternatives.
评论 #40503396 未加载
评论 #40443204 未加载
评论 #40442201 未加载