Thread (10 messages) flat view 10 messages, 8 authors, 2016-06-15
  • Darcs · Bu Bacoo <hidden> · 2016-06-15
  • Re: Darcs · Linus Torvalds <torvalds@linux-foundation.org> · 2016-06-15
  • Re: Darcs · Martin Langhoff <hidden> · 2016-06-15
  • Re: Darcs · Jan Hudec <hidden> · 2016-06-15
  • Re: Darcs · Theodore Tso <tytso@mit.edu> · 2016-06-15
  • Re: Darcs · Junio C Hamano <hidden> · 2016-06-15
  • Re: Darcs · Linus Torvalds <torvalds@linux-foundation.org> · 2016-06-15
  • Re: Darcs · Josh Triplett <hidden> · 2016-06-15
  • Re: Darcs · Johannes Schindelin <hidden> · 2016-06-15
  • Re: Darcs · Bu Bacoo <hidden> · 2016-06-15

Re: Darcs

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:18

"Martin Langhoff" [off-list ref] writes:
quoted
"Academic".
OTOH, and from the POV of someone closely following the SCM tools in
the last few years (and using almost all of them), darcs was the first
usable DSCM in the camp. I am not sure how much of its commandline
user interface was borrowed from BK or elsewhere, but darcs was
_easy_, where Arch was extremely hard to use.
I second this.  Before I started contributing to git in its
early weeks, I staged my own changes to my day-job project in
darcs to trickle them in to the company's central repository (I
was sufficiently faster than other members of the project and I
had to pace myself). 

It would have been much more difficult for me to grasp the basic
concepts of how "distributed development" process works, if I
did not have an exposure to Darcs before I started, especially
because I never used BK.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help