Commits


CHANGES for 0.83


regress: commit coverage for the new logmsg ref feature This tests we correctly: - use multiple logmsg refs in one commit; - use only relevant refs involving affected paths; - use refs when some of the affected paths are reverted; - neither use nor remove refs if all affected paths are omitted from the commit; - use refs when previously excluded paths are later committed. - remove corresponding temp merged_log 'got-logmsg-*' files hints and ok stsp@


got: don't leave tmp "got-logmsg-*" files in the work tree Reported by stsp on irc, and reviewed as part of the following regress commit covering the commit aspect of logmsg refs. Delete temp merge_log files if created during commits involving backed-out/cherrypicked changes. ok stsp@


gotsh.1: show how to set up anonymous public read-only repository access


use VISUAL instead of EDITOR in histedit_mesg_filemode_change VISUAL is preferred and relying on EDITOR may cause test failures in some environments. pointed out by op and jamsek


simplify file content comparison in a regress test; suggested by op@


fix histedit -m on a commit which only changes filemode bits The commit was being miscategorized as a no-op change and dropped. Now the commit is retained and its log message is updated as expected. ok op, jamsek


remove TODO item regarding 'got send -d' support in gotd


got.1: editing merged log messages is no longer optional, tweak related wording


got.1: Mark the commit argument to cherrypick and backout optional patch by Josiah Frentsos


abort commit with merged log messages if the log message is left unmodified ok op@


avoid creation of temporary file if no merged log messages will be used


rename a variable for clarity


clarify documentation of cherrypick/backout log message recording ok jamsek


uppercase cherrypick/backout -X progress output ok jamsek