Commits


when "bad path" errors occur, always show the path in question


properly free cmd_argv in tog's main() function


fix typo in comment; found by mpi@


show merged commit ID + logmsg upon merge conflict during rebase and histedit This makes it more apparent which commit contained the conflicting change. The new output looks like this: C sys/dev/pci/if_iwm.c 8a98d848a1a5 -> merge conflict: properly modify station queues got: conflicts must be resolved before rebasing can continue


don't leak logmsg in show_rebase_progress()


in got.1, clarify that rebasing of branches with zero local changes is normal


bump version number


changes for 0.28


attempt to more clearly explain what 'got rebase' is used for


disallow 'got rebase' while a histedit operation is in progress


document that 'got integrate' cannot be used during a histedit operation


document histedit's -F option


explain more clearly how a histedit script will be edited


document more clearly what needs to be done to start a histedit operation


switch 'got tag' commit argument to a -c option for consistency


let 'got branch' switch and update the work tree ok tracey


edit man page wording for histedit -m feature


Sync the description of the -r flag from "tree" to the other commands. Clarify that if the current directory is a work tree, tog will pick the repository associated with this work tree by default. ok stsp


add 'got histedit -m' option which makes it easy to edit log messages only ok tracey


show how to log subdirectories in got.1 EXAMPLES ok naddy


switch "tog diff" repository path argument to a new -r option


fix "tog diff object1 object2" by actually extracting the repository path from the work tree


document semantics of got log and tog log path arguments


add ^B/^F key bindings for page up/down in the "blame" and "tree" views


disable compiler warnings in release builds because -Werror is bad for ports sthen@ suggested to drop -Werror; I think we don't need any -W in release mode