dvcs   4335

« earlier    

Re: [9fans] There is no fork
> I struggle to understand how version control is not more actively used.

It's not particularly necessary when you have global state with snapshots provided by a shared WORM fs. DVCS adds a lot of complexity for questionable gain, in that environment. 9front's adoption of mercurial is a historical accident rather than a desired outcome. But, I understand that most people just want to use the tools they already know. It's much easier than learning a new paradigm.
piperesearch  dvcs  plan9  comment 
9 days ago by mechazoidal
version control - What does Linus Torvalds mean when he says that Git "never ever" tracks a file? - Stack Overflow
PR: "In my taxonomy the term for what we're interested here is the 'atomicity' of the version control system. [...] When a VCS has file-level atomicity, there is in fact a history for each file. The VCS must remember the name of the file and what occurred to it at each point. Git doesn't do that. Git has only a history of commits—the commit is its unit of atomicity, and the history is the set of commits in the repository. "
"Note that a VCS can be commit-oriented, yet still store data file-by-file. That's an implementation detail, though sometimes an important one, and Git does not do that either. Instead, each commit records a tree, with the tree object encoding file names, modes (i.e., is this file executable or not?), and a pointer to the actual file content. [and contents in blobs]"
"The file history you see [with 'git log'] does not exactly exist in the repository, in some sense: instead, it's just a synthetic subset of the real history. You'll get a different "file history" if you use different git log options!"
(there's also his VCS book linked)
piperesearch  git  stackoverflow  answer  dvcs 
4 weeks ago by mechazoidal
Gregory Szorc's Digital Home | The Mercurial Revlog
PR: "In theory, Mercurial revlogs can be backed by anything. This is the extensibility of Mercurial at work. There's just a Mercurial extension sitting between using SQL, S3, Cassandra, or any other storage backend for revlogs."
Note that he warns that there can be impedance mismatch with using alternate revlog backing(bundles are the linchpin), but I think this may have been fixed with bundle format v2
2014  dvcs  hg  datastructures  version_control  piperesearch 
august 2019 by mechazoidal
patience diffing algorithm
tedu: "I needed a (text) diff algorithm, and if you search for one you mostly come up with the Myers algorithm. But then I stumbled across something called patience diffing, and it turns out to be just what I wanted. It’s already described elsewhere, but it seems more people could stand to know about it, so here we are. It’s easy to understand, and more importantly, usually makes pretty diffs (often prettier than Myers). "
algorithms  diff  dvcs 
august 2019 by mechazoidal
Finding a New Git Host | Lobsters
Sourcehut author weighs in on email for patch management

Also note "ForgeFed", an ActivityPub proposal to add git commands
lobsters  discussion  hosting  dvcs  2019 
august 2019 by mechazoidal
git-up/GitUp: The Git interface you've been missing all your life has finally arrived.
Work quickly, safely, and without headaches. The Git interface you've been missing all your life has finally arrived.
git  dvcs  macos  opensource  software 
june 2019 by ssorc
The Future Is Federating Forges - C+J Slep
This is an overview/thinking-out-loud of software forges like GitHub, and how to get them into the fediverse. There is compare/contrast with git's email system, along with acknowledging that ActivityPub is still difficult to work with. And of course the "what happens if a node goes down permanently"
PR: for the support structure, terminology, and some ideas (compare to Art of CG Supervision)
activitypub  dvcs  fediverse  piperesearch  2019  federation  collaboration 
may 2019 by mechazoidal
VFS for Git: Git at Enterprise Scale
The Virtual Filesystem for Git (formerly GVFS) is an open source system that enables Git to operate at enterprise-scale. It makes using and managing massive Git repositories possible.
git  microsoft  dvcs  filesystem  opensource  software  tools 
may 2019 by ssorc
sillsdev/chorus - End-user collaboration library via 3-way xml merging and hg dvcs under the hood
Chorus is a version control system designed to enable workflows appropriate for typical language development teams who are geographically distributed. These teams need to edit a set of common files, working towards a publication. They want to share their work while, crucially, being able to defer dealing with conflicting edits for periods of time or until a qualified team member can make decisions about the conflicts. The system is implemented on top of a commonly-used Open Source Distributed Ve...
dvcs  mercurial  xml  merge 
april 2019 by spl
Version Control Before Git with CVS
If your software engineering career, like mine, is no older than Github, then Git may be the only version control software you have ever used. While people sometimes grouse about its steep learning curve or unintuitive interface, Git has become everyone’s go-to for version control. In Stack Overflow’s 2015 developer survey, 69.3% of respondents used Git, almost twice as many as used the second-most-popular version control system, Subversion.1 After 2015, Stack Overflow stopped asking developers about the version control systems they use, perhaps because Git had become so popular that the question was uninteresting.
git  dvcs  vcs  programming 
february 2019 by spky

« earlier    

related tags

2014  2017  2019  activitypub  algorithm  algorithms  alternative  answer  app  aprilfools  architecture  asspad  autosync  best.practices  best  bitbucket  bitcoin  blockchain  book  branches  branching  build  business  cd  chat  cheatsheet  ci  cli  client  cockroachdb  code  codereview  coding  coin  collaboration  commandline  comment  commons  community  compare  comparison  config  continuousdelivery  continuousintegration  control  cookbook  critique  crowdfunding  cryptocurrency  culture  curses  cvs  darcs  data  database  databases  dataset  datastructures  decentralized  developer  development  devops  diagrams  diff  discussion  distributed-systems  distributed.version.control  distributed  dlt  documentation  dropbox-alternative  dweb  economy  emacs  evolution  explained  facebook  federation  fediverse  filesystem  fork  foss  fossil  freebsd  frontend  ftrain  functional  funny  git  gitflow  github  github_repos  gitlab  go  gogs  golang  google  goto  governance  gui  haskell  hci  helper  hg  hosted  hosting  howto  humor  ifttt  important  incomprehensible  infrastructure  interface  ipfs  jargon  language  learn  learning  linearizability  linux  lisp  lms  lobsters  mac  macos  management  mercurial  merge  microsoft  module  monorepo  msft  mt  newbie  offlinefirst  opensource  p2p  pandoc  patch  patches  paul.ford  phabricator  pijul  piperesearch  plan9  pmo  process  productivity  programming  protocol  python  qa  radicle  rebase  refactoring  reference  release  releasemanagement  replication  repository  review  rust  scm  scripting  scuttlebutt  sendtokindle  serializability  server  service  shell  software  softwareengineering  source-control  spanner  stack  stackoverflow  starred  statemachine  sublimetext  subversion  sustainability  svn  synchronized-folder  teach  technology  text  theory-of-patches  theory  thisvsthat  time  tips  tool  tools  topology  tutorial  usability  use  value  vc  vcs  version-control  version  version_control  versioncontrol  video  visualisation  visualization  webapp  wiki  windows  workflow  xml 

Copy this bookmark: