Commits


some log -b documentation escaped the previous backout commit


backout 499d7ecc534806c7daf8795b1c9f76575520921f It is better to use another option code for first-parent log. Having a -b option which takes no argument is too confusing. E.g. 'got log -b foo' would log the path 'foo', not branch 'foo' and I got confused by that myself already...


initial 'got import' implementation


clarify usage of 'got rebase' options in man page


clarify our intentions regarding clone/fetch and the master branch


show how to create a commitable diff in got.1 EXAMPLES


avoid cross-references to git-gc(1)


update CAVEATS section in got.1


fix wrong command listed in man page text


man page wording tweak


more clearly document the effect of 'got branch -d'


make 'got branch -l' indicate work tree's current branch


'got rm' -> 'got remove' in man page


rebase man page tweaks


prevent rebase in a work tree with an incompatible path prefix


disallow 'got update' and 'got commit' while rebase is in progress


handle no-op changes during 'got rebase -c'


man page wording fix


initial 'got rebase' implementation


rename 'got cherrypick' alias 'got ch' to 'got cy'


rename 'got rm' to 'got remove'; keep 'rm' as an alias


require user to type full got command names or short aliases The previous strncmp-based approach was problematic, e.g. "co" was treated as an alias for "commit", while most users will expect "co" to map to "checkout". Introduce explicit aliases and document them.


write 'message' out as a full word in 'got commit' documentation


fix incomplete documentation of 'got checkout' -c option


document the 'abbreviated SHA1 argument' feature