Kim Altintop

Results 47 issues of Kim Altintop

We rely on execve'ing `git` in some places, which should be feature-gateable.

We should be able to preserve existing unknown trailers, which is currently not straightforwardly doable.

It is not strictly required to own the signing key when pulling through the remote helper. Depends on #461, and allowing the local transport to inspect at runtime whether it...

Reminder for self to send upstream patches (aftermath of #369) where `libgit2::git_reference_normalize_name` disagrees with `git-check-ref-format`: * A refname consisting of a single `@` should be rejected * A multi-segment refname...

bug
brooming
git

We do not currently support removing a namespace (aka "repo"), due to the following limitations: 1. There are no transactional operations on the refdb 2. We do not keep track...

enhancement
git
prio:low

This would require protocol support for efficiently computing the intersection of URNs two peers have locally. As a first step, however, we can just implement it as a loop which...

`proptest!` has a bit of a hygiene problem, and may unexpectedly use up your scrollback buffer to draw an [ancestry of parenthesis](https://imgs.xkcd.com/comics/lisp_cycles.png) up to approx. the invention of the number...

enhancement
good first issue
help wanted
brooming
testing

There are some opportunities for boggeling of mind and situations in which in-band upgrade of identities will not be able to make progress. Detailing the verification (that is, history fold)...

In order to be able to check out a working copy from the storage backend (aka "monorepo"), the remote end must announce the HEAD symref, pointing to a valid default...

Specify what exactly is verified, and what happens if a signature does not verify (ie. stop replicating that "topic")