Ah, the world of changes. Always changing things are. And keeping track of changes can be quite the challenge. Thankfully we have version control systems to make the chore a bit easier. But review these changes and we find our output options limited. That's were VCLog comes in. Learn More...
Copyright (c) 2009 Rubyworks. All Rights Reserved.
How about a Change Log in glorious technicolor!
Or a Release History to make you feel like a schoold girl with a box of crayons.
VCLog can provide a changelogs in a variety of uniform formats for different SCMs. If we ask vclog for help will see it's commandline interface is fairly self-explanatory.
$ vclog help
Usage: vclog [TYPE] [OPTIONS]
OUTPUT TYPE: (choose one)
changelog display a Change Log
history display a Release History
version display the current tag version
bump display next reasonable version
list display format options
help show help information
Help for generating a Change Log looks like this:
$ vclog log --help
Usage: vclog [changelog | log] [options]
Print a Change Log.
OUTPUT OPTIONS: (use varies with format)
-f, --format FORMAT output format
--style provide a stylesheet URI (css or xsl) for HTML or XML format
-t, --title TITLE document title
-d, --detail provide details
--id include revision id
-l, --level NUMBER lowest level of commit to display [0]
SYSTEM OPTIONS:
--debug show debugging information
-h, --help display this help information
Without any format selected, vclog will use the ANSI-colored GNU-like format.
Here is an example of the non-colored GNU format.