Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by rjbs (4671) on 2009.08.09 14:27 (#69935) Homepage Journal

    I find it helps to not talk about the "branch" master but rather the "head" master. When you separate the fact that heads can cause branching from their essence, you can think of more ways to use git.

    So, make a new head called "last-summary." Start it at commit x, presumably the current location of master.

    In two weeks, get the output of `git log last-summary..master` and you will see all the changes that are between the two named commits. With that summary generated, you can now move last-summary to the same place as master. master will keep moving, while last-summary serves as a bookmark.

    This is one of the many ways that heads are useful: they're mobile tags.

    --
    rjbs