4 ms·

Does anyone know whether fossil has a staging area? I tried but could not find it. Google didn't really help either.

by teh 15y ago

gecko 15y ago
Fossil does not have a staging area. Instead, like Mercurial, it encourages you to stash things you do not plan to commit.
- etherealG 15y ago
  if you stash everything you're not committing, then the working copy becomes the staging area, and the stash becomes the working copy. how is that any different? seems to me both systems have a method of choosing what to commit, in git you can choose to stash or stage, in the others you can only stash since they "don't have a staging area". git++ for having both options.
  - prodigal_erik 15y ago
    Git has many commands which allow fine-grained manipulation of the staging area; stashes are a crude afterthought in comparison. The problem is that highly encouraged workflows like "git add --patch" inevitably lead to toxic commits which were never tested because they never truly existed in the workspace.
    - hammerdr 15y ago
      Commits aren't dangerous until you push them. You can very easily rebase out a committed patch after you've tested it.
      - etherealG 15y ago
        with great power comes great responsibility :)
- philwelch 15y ago
  Does it have a patch mode for stashing? Use case: A commit should only do one thing at a time, but sometimes I'm not as organized. I like to do a whole mess of work and when I'm ready to commit it, I use git add --patch to separate out unrelated bits of work into separate commits--even if separate bits of work end up in the same file. It's amazing how much a load off your mind this is--you don't have to be quite as OCD while you're coding if you're a little fastidious about your commits later on.
  - __david__ 15y ago
    I pretty much exclusively commit like that nowadays. I use commit-patch (http://porkrind.org/commit-patch http://porkrind.org/commit-patch) which is a pretty thin layer around git but also has emacs integration so you can just diff, edit your hunks with emacs hunk editing tools and then commit the patch. I can't imagine using a VC without the capability any more...

Does anyone know whether fossil has a staging area? I tried but could not find it. Google didn't really help either.

by teh 15y ago

Does anyone know whether fossil has a staging area? I tried but could not find it. Google didn't really help either.

gecko 15y ago

Fossil does not have a staging area. Instead, like Mercurial, it encourages you to stash things you do not plan to commit.

etherealG 15y ago
if you stash everything you're not committing, then the working copy becomes the staging area, and the stash becomes the working copy. how is that any different? seems to me both systems have a method of choosing what to commit, in git you can choose to stash or stage, in the others you can only stash since they "don't have a staging area". git++ for having both options.
- prodigal_erik 15y ago
  Git has many commands which allow fine-grained manipulation of the staging area; stashes are a crude afterthought in comparison. The problem is that highly encouraged workflows like "git add --patch" inevitably lead to toxic commits which were never tested because they never truly existed in the workspace.
  - hammerdr 15y ago
    Commits aren't dangerous until you push them. You can very easily rebase out a committed patch after you've tested it.
    - etherealG 15y ago
      with great power comes great responsibility :)
philwelch 15y ago
Does it have a patch mode for stashing? Use case: A commit should only do one thing at a time, but sometimes I'm not as organized. I like to do a whole mess of work and when I'm ready to commit it, I use git add --patch to separate out unrelated bits of work into separate commits--even if separate bits of work end up in the same file. It's amazing how much a load off your mind this is--you don't have to be quite as OCD while you're coding if you're a little fastidious about your commits later on.
- __david__ 15y ago
  I pretty much exclusively commit like that nowadays. I use commit-patch (http://porkrind.org/commit-patch http://porkrind.org/commit-patch) which is a pretty thin layer around git but also has emacs integration so you can just diff, edit your hunks with emacs hunk editing tools and then commit the patch. I can't imagine using a VC without the capability any more...