Commits


do not forget to create references under remotes/origin during 'got clone'


create a git config file in newly cloned repositories


apply unveil(2) to 'got clone'


pledge 'got clone'


sync got clone's usage with reality


only print fetch progress to stdout if something has changed


move to a less hectic progress display again


more fine-tuning of fetch progress display


tweak indexing progress output again: display raw object counters


create repository before connnecting and print a message when connected


tweak progress display


rewritten got-index-pack; sorry about the monster commit


send indexing progress via an imsg


send pack file download progress information over imsg


add support for git protocol sidebands and display server progress


remove unused arguments from got_fetch_pack()


rename got_fetch() to got_fetch_pack()


attempt to connect to a server before creating a local repo


make got_fetch() provide reference info to callers and set refs in cmd_clone()


have got_fetch() require an open got_repository to be passed in


make got_fetch() expect URI information in parsed form


rename got_clone() to got_fetch()


declare got_clone() in public API space


Add initial support for network protocol. Ported from git9 by Ori Bernstein.


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.