I think in most cases you want the dependencies between commits that darcs removes. For instance, let’s say you have three patches:

  1. Create hello.sh with echo Hello World
  2. Create lib.sh with hello() {echo Hello World}
  3. Edit hello.sh to source lib.sh; hello

Of course, in this case it would be easy to manually specify the dependency (3 depends on 2) and unlike git 2 wouldn’t have to depend on 1. But for a larger project I’m imagining always having to look at the current path set to figure out dependencies and the git model of “every commit depends on the patch before” seems better for large codebases.

But I could be wrong. I’d be curious to see what a large darcs repo looks like.

General Programming Discussion

    A general programming discussion community.


    1. Be civil.

    Other communities:

    • /c/rust
    • /c/python
    • /c/powershell
    • /c/haskell
    • /c/fpcomplete
    • /c/cpp
    • /c/c_programming
    • /c/julia
    • 0 users online
    • 1 user / day
    • 6 users / week
    • 17 users / month
    • 127 users / 6 months
    • 2500 subscribers
    • 670 Posts
    • Modlog