Commits


add -d option to 'got fetch' for deleting old branches and tags


add support for listing remote branches and tags to 'got clone' and 'got fetch'


add support for fetching specific branches to 'got clone' and 'got fetch'


got.1 wording tweak for clarity


got.1 wording fix


man page wording simplification: target-direcory -> directory


got(1) man page wording tweak


line to git-repository(5) for details about pack files


document what got-index-pack does


fetch only HEAD branch and tags by default; add -a option to fetch everything


document use of port numbers in URLs


in got.1 EXAMPLES, move the 'got integrate' example further up


add support for repository mirrors to 'got clone' and 'got fetch'


re-add chatty mode to got-fetch-pack; it will be useful to diagnose bugs


implement 'got fetch'


document 'got cl' alias for 'got clone'


move clone code and documentation up so it appears before checkout


allow controlling verbosity of 'got clone' with -q and -v options


man page updates for 'got clone'


add ori as author


prevent commits from being listed more than once in a histedit script While merging a commit multiple times during a histedit operation could potentially make sense in some corner case, a commit appearing more than once in the script is more likely to happen accidentally. If desired, the same effect can still be achieved by running multiple histedit operations, or by using 'got cherrypick' while the histedit operation is paused for arbitrary editing.


be helpful when users try to check out work trees without a known branch Provide a useful error message in such cases and explicitly document intentional restrictions in the got(1) man page. Prompted by a question from Adam Steen via bsd.network https://bsd.network/@adams/103768951483318235


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


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


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