The from and via lines were deliberately adjacent before, so they should stay that way.

Shown as "orig:" in the output. Slightly adjusts a rebase regress test to the new output.

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.

its only usage was removed in e77c4c9f24 but the define remaied. ok stsp.

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

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

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().

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.

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).

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@

part of a larger diff that's ok stsp@

The counterpart of generating v3 bundles is to load them.

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.)

in a few cases, an array of SHA1_DIGEST_LENGTH has been converted to a struct got_object_id to simplify the handling.

suggested by stsp