vonc + versioncontrol   146

Git Branching Model
We tried to explain how we can build a branching model for Git
git  branching  model  slides  rebase  merges  pros  cons  branch  presentation  code  tools  versioncontrol  collaboration 
december 2015 by vonc
Home // Think Like (a) Git
When you're just getting started, something as straightforward as a merge can be terrifying. It can take a long time to really become comfortable using some of Git's more advanced features. (It took me a year or two.)

Once people achieve some level of Git enlightenment, they tend to make statements of the form 'Git gets a lot easier once you realize X' -- but that doesn't do much for people staring up Git's steep learning curve.

My goal with this site is to help you, Dear Reader, understand what those smug bastards are talking about.
help  source-control  scm  versioncontrol  howto  reference  tutorial  git 
september 2013 by vonc
Version Control for Multiple Agile Teams
The version control pattern Branch owner & policy The "done" concept The Done branch When do we create additional branches? Work branches Publishing from work to trunk What if our team implements multiple stories in parallell? Done includes regression testing! Diverging code (merging conflicts) Multiple teams - what if other teams are publishing to the trunk as well? Release branches The big picture
perforce  versioncontrol  scrum  cvcs  merge  done  branch  svn  release 
june 2013 by vonc
10 things I hate about Git « Steve Bennett blogs
Git is the source code version control system that is rapidly becoming the standard for open source projects. It has a powerful distributed model which allows advanced users to do tricky things with branches, and rewriting history. What a pity that it’s so hard to learn, has such an unpleasant command line interface, and treats its users with such utter contempt.
mercurial  criticims  quality  dvcs  vcs  article  versioncontrol  github  rant  git 
august 2012 by vonc
My Problem with Git: No Abstraction | The Geek Law Blog
In other words, mv combines two conceptual functions into one thing, simply because that’s the underlying implementation.

And I realized that this kind of “implementation leakage” occurs with many git commands. The non plus ultra evidence is the excellent post, Git Reset Demystified by Scott Chacon. It’s about git’s equivalent to svn revert

A great related post: On git and usability
Michael Feathers takes the opposite point of view: My Satisfaction with Git: No Abstraction.
criticims  abstraction  vcs  versioncontrol  opinion  git  -  Fast  Version  Control  System 
may 2012 by vonc
« earlier      
per page:    204080120160

related tags

-  3.7  3.8  abstraction  add  advantages  advice  agile  aix  algorithm  algorithms  alias  aliases  alternative  amend  amp  animation  api  article  atelier  atlassian  bare  basics  bazaar  beginner  bestpractices  blame  blog  book  books  branch  branching  build  c#  cheat  cheatsheet  checkout  chown  churn  ci  clearcase  code  codereview  collaboration  Commands  commit  commits  comparaison  comparison  compose  computers  concepts  concurrency  config  configuration  conflicts  cons  content  continuous  continuous_integration  control  conventions  copy  cours  course  criticims  criticisms  critics  cvcs  cvs  cygwin  d3  database  db  debian  definition  deployment  design  dev  developer  development  development-process  diagram  difference  directory  disadvantages  disavantages  distributed  doc  docker  documentation  done  dropbox  drupal  dvcs  ebook  eclipse  editing  editor  elm  english  enterprise  ericraymond  example  explanation  export  external  fast  fastforward  feature  features  fetch  file  format  forum  free  frequance  fun  funny  gem  generic  gerrit  git  git-flow  git-svn  gitbook  gitconfig  gitflow  github  gitignore  gitinternals  gitlet  gitolite  gitosis  gitscreencasts  go  golang  good  good-practices  google  graft  graph  graphic  graphics  gui  guide  hate  helix  help  hg  history  hook  host  hosting  howto  html  humor  humour  ibm  ignore  illustrated  illustration  image  images  import  important  improvment  index  installation  integration  intellij  interfaces  internal  introduction  java  JavaScript  jdk  joke  koan  koans  large  latex  launcher  leak  leaking  learn  learning  levels  linefeed  links  linux  list  local  log  logs  management  manager  markdown  master  maturity  maven  mercurial  merge  merges  merging  message  migration  model  mono  msys  msysgit  must  naming  newline  nosql  number  numbering  object  online  openjdk  opensource  opinion  option  ours  packages  pain  pantheon  patch  pattern  pdf  perforce  performance  perl  php  pickaxe  picture  pictures  pin  plasticscm  plugin  policy  powershell  practices  pre-cfommit  preferences  presentation  problem  production  programming  project  projectmanagement  promiscuous  pros  publication  pull  push  python  quality  rails  rant  rational  rcs  rebase  recovery  refactoring  reference  references  reflog  reintegrate  release  repository  resource  resources  review  revison  revolution  rfc  rosetta  ruby  rubygems  rust  rust-lang  schema  scm  screencast  scrum  security  semantic  server  setup  sha1  should  single  size  slides  so  software  solaris  solaris10  source  source-control  sourcecontrol  source_control  specification  split  sql  ssh  stackoverflow  stage  staging  standalone  stone  strategy  structure  studio  submodule  submodules  subproject  subprojects  subversion  survey  svk  svn  switch  sysadmin  system  table  text  tfs  theirs  tips  tool  tools  toread  tortoise  tortoisegit  tree  tutorial  tutorials  tweet  ubuntu  uncle-bob  unit  unix  update  upgrade  vcs  version  version-control  versioncontrol  versioning  versionning  video  visual  visualization  visualstudio  vs2010  web  webdesign  whatis  wiki  windows  wordpress  workflow  workflows  wrapper  writing  zit 

Copy this bookmark: