version_control   2223

« earlier    

Chris's Wiki :: blog/tech/VCSVsMetadata
But, unfortunately, I've come to believe that there are practical
issues for VCS usage that conflict with capturing and restoring
metadata, especially once you get into advanced cases such as file
attributes. Finally, you
have to decide what to do if you can't restore a particular piece
of metadata on checkout (either because it's not supported on this
system or because of various potential errors). This is a perfectly sensible decision for what they're aimed at,
in line with how current VCSes don't do well at handling various
sorts of encoded data (starting with JSON blobs and moving up to,
say, word processor documents). Would it be nice to have a perfect VCS, one that captured everything,
could restore everything if you asked for it, and knew how to give you
useful differences even between things like word processor documents? Current VCSes explicitly make the tradeoff that they
are focused on plain text files in situations where only some sorts of
metadata are important.
Git  version_control 
4 days ago by sechilds
Do your commits pass this simple test?
version_control  patterns  writing  best_practice 
9 weeks ago by archangel
The History of Version Control
noting that the simple linear-based workflows are "good enough" for most creative industries: "Watching something evolve over time often eliminates confusion. It makes the conversation around the finished product much more productive. Most importantly, it instantly establishes trust among everyone invested. [...] That is to say, merely recording the history of files over time will suffice rather than worrying about how to merge different sets of work."
piperesearch  version_control  history  tumblr 
9 weeks ago by mechazoidal
Managing generated files in GitHub
How to suppress the diff view of generated files.
version_control  tips 
10 weeks ago by archangel

« earlier    

related tags

!to_tag_bit  %stack_overflow  2017  2018  @devenvironment  @wikimedia  agile  alternatives  analytics  architecture  archive  automation  bazaar  beruf  best_practice  bestpractices  bitbucket  blog  bookmarked_on_site  books  branching  build_tool  cartoon  change_log  cheatsheet  ci  code  code_changes  code_quality  code_review  codesnippets  coding  collaboration  commit  commits  communication  comparison  computers  continuous_deployment  continuous_integration  control  criticism  crypto  cvs  database  deployment  design  dev  development  development_process  devops  discrimination  diy  docker  documentation  dvcs  ebook  editors  email  files  fossil  fpga  gerrit  git  gitbucket  github  gitless  graphic_design  gui  history  home_page  howto  humor  interview  java  java9  kindle  kubernetes  learning  links  linux  management  markdown  mediawiki  merge  monorepo  npm  official_sites  open_science  opensource  osx  patterns  php  piperesearch  process  production  productivity  programme  programming  programming:best_practices  psychology  python  quotes  rebase  reference  release  resources  ruby  scott_hanselman  security  semantic  semantic_versioning  semver  shell  sketch  software  software_development  sql  staging  statistics  sublime  subversion  svn  system_admin  teaching  teaching:coding  teaching:programming  templating  tip  tips  to_read  to_teach  to_try  tool  tools  tumblr  tutorial  tutorials  updates  ux  vcs  vector  version  versioning  web  web_design  web_development  webdev  why_not  wishlist  wordpress  workflow  writing 

Copy this bookmark: