Baltasar Dinis 64ea8bee47 git: reject remotes with forward slashes ...

Although this behaviour is accepted by git, it's a degenerate case.
Especially because we implicitely rely on being able to parse out the
remote from the refname (i.e., `refs/remotes/<remote>/<branch>`).

Branches can have forward slashes, but if remotes can also have them,
parsing the refname becomes ambiguous, and a pain. Especially because it
would be totally legal to have a branch "c" on remote "a/b" and a branch
"b" on remote "a".

Fixes #5731

2025-02-18 07:10:01 +00:00

..

benches

style: add semicolon at the end of expressions used as statements

2024-10-04 22:29:13 +02:00

gen-protos

cargo: inherit lints configuration from workspace

2024-10-04 22:29:13 +02:00

proc-macros

style: remove useless uses of .iter()

2024-10-04 22:29:13 +02:00

src

git: reject remotes with forward slashes

2025-02-18 07:10:01 +00:00

tests

local_working_copy: short-circuit update when tree is unchanged

2025-02-17 18:59:56 +00:00

testutils

repo: move rebase_descendants_with_options_return_map() to tests

2025-01-18 01:21:28 +00:00

Cargo.toml

lib: remove use of zstd

2025-01-08 22:02:21 +00:00

LICENSE

cargo: add LICENSE file to each crate we publish

2023-09-22 21:48:28 -07:00