fix argument name in header declaration

fix order of header lines: from, via, date, orig The from and via lines were deliberately adjacent before, so they should stay that way.

tog log: show author dates if showing author names (@)

tog: show author date if different from committer date

got: show author date if different from committer date Shown as "orig:" in the output. Slightly adjusts a rebase regress test to the new output.

got rebase: preserve author dates

do not talk about "SHA1 checksum"s in documentation comments these functions are really taking a struct got_object_id or depend on the hashing algorithm of the repo so update the comments to match the reality.

regress: do not hardcode http port

remove only use of GOT_WORKTREE_INVALID_COMMIT_ID its only usage was removed in e77c4c9f24 but the define remaied. ok stsp.

delete trailing whitespaces

minor touches to got-worktree(5) - stop mentioning SHA1, it's not the only hashing algorithm supported now - s/lockf/flock since we use flock(3) ok stsp@

gotwebd: add support for an "owner" file Was requested in the IRC channel some time ago. The "owner" file is also supported by stagit. tweaks stsp and tracey, ok stsp

gotwebd: avoid unnecessary strdup() It's fine to leave the owner set to NULL in case there is none. The template {{..}} construct accepts NULLs (rendering an empty string), and repo_dir->owner is only passed to that or to free().

gotwebd: refactor file load in its own routine Split gotweb_load_file() out of gotweb_get_repo_description() and reuse it for gotweb_get_clone_url() too. Will be useful in the future for other tasks too.

run more tests in sha256 mode Since we've been quickly expanded the support for sha256, instead of making the regress "opt-in", make them "opt-out". Basically, only the regress that are reaching the network protocol code needs to be disabled as of now in sha256 mode (until we add support for git protocol v2).

gotadmin: add flag to `init' to choose the hashing algorithm Do the same for `got init' too obviously. Repositories created via `clone' are implicitly sha1 since we don't speak the v2 protocol (yet). ok stsp@

gotadmin: show hashing algorithm in `info' output part of a larger diff that's ok stsp@

load: support bundle v3 The counterpart of generating v3 bundles is to load them.

generate bundles v3 when in sha256 repos bundles v2 don't have a way to specify the object-format and so they can't work in sha256 mode; v3 adds a some "capabilities" so that it's possible to specify the object-format (and also other things that we aren't interested in actually.)

support to create/index sha256 packfiles in a few cases, an array of SHA1_DIGEST_LENGTH has been converted to a struct got_object_id to simplify the handling.

create sha256 bare objects

fileindex: improve unexpected object-format error message suggested by stsp

add sha256 support to the worktree and fileindex code

simplify trim_obj_id(): replace echo|sed with expr(1)

fix got_object_id initialization when parsing off a delta