On Tue, May 28, 2013 at 11:05 AM, Laurens Van Houtven <_...@lvh.io> wrote:
>
> My question about how this process with the "pending-review" branch works
> was more about the mechanics of how you'd use such a branch to facilitate
> code review. What goes in that branch? How does it get there? What is the
> sequence of fossil commands?
>
You can create the branch as you do the comment. For example:
fossil commit --branch pending-review
Or
fossil commit --branch experimental
If you forget to do it then, you can always visit a check-in after it is
committed and click on the "Edit" link to do things like revise the
check-in comment, update the check-in time, or move the check-in to a
different branch (such as "experimental" or "pending-review" or "mistake").
Sometimes somebody will check-in a change to trunk that I don't agree
with. When that happens, I just move their check-in off into a branch.
A tangent: Note that when you "edit" a check-in, you are not really
changing the check-in. You are, instead, adding additional information.
Fossil does not erase or modify, it only augments. The original check-in
comment, and time, and branch are all still there for anybody to see. By
'editing' the commit, you are adding a new record to the repository that
says "for display purposes, modify checking XYZ as follows..."
Notes also that Fossil allows you to start a new branch named (for example)
"experimental" even if there already exists one or more other branches with
the same name. At
http://www.fossil-scm.org/fossil/timeline?n=200&r=experimental it looks
like there are a dozen or more "experimental" branches currently in the
Fossil tree.
--
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
