Re: publish from certain commit onward, keeping earlier history private, but provable

e/scm/git/docs/git-replace.html -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature

Re: Signed tags and git repository

rson and want to make the signature public, or make a local signature which is local to your keyring and won't be sent to eg keyservers. Or just mark the key as trusted overall. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature

Re: Three dot notion used inconsitent?

A...B is defined as all the commits from a comman ancestor of A and B, up to B. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature

Re: [PATCH] Consider object stores in alternates during a dissociating clone

git-send-email instead. There's even an example configuration for gmail in the manpage. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature

Re: Eric Sunshine mail delivery failure

according to RFC2181. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature

Re: [PATCH v2] commit: add commit.signoff config option

that since we have `git commit -s`, which is just as easily added as a really simple git alias. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature

Re: Untracked files when git status executed on a new folder

, the folder created in step 1 appears as untracked. Can't reproduce on Git 2.4.4/Linux, which Git version and platform are you using? -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature

Re: Submodule and proxy server.

On 22/06, Jamie Archibald wrote: fatal: unable to access 'http://http://path/to/submodule/MySubmodule.git/': The requested URL returned error: 502 Did you copy this error verbatim? -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias

Re: [PATCH v2] upload-pack: Fail if cloning empty namespace

toward, considering your last reply to the other thread,) then ref namespaces won't really work in most cases, and it seems pointless to support them at all. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP

Re: [PATCH v2] upload-pack: Fail if cloning empty namespace

On 20/06, Junio C Hamano wrote: Johannes Löthberg johan...@kyriasis.com writes: On 15/06, Junio C Hamano wrote: You would probably want new tests, but more importantly did you make sure this passes existing tests? It seems to break 5509 (there could be others) at least for me. It breaks

Re: [PATCH v2] upload-pack: Fail if cloning empty namespace

so that you eg can only push to specific namespaces. Having it be created is especially important when someone might be working on the same machine as the repo, where the push won't go through eg SSH. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com

Re: GitHub Pull Request merge commands

was about? If not, why? ;-) A pull request is about all commits in the branch, which is why topic-branches should be used for PRs. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature

Re: [PATCH v2] upload-pack: Fail if cloning empty namespace

On 13/06, Johannes Löthberg wrote: Git should fail to clone if trying to clone from an non-existing ref namespace, since it's the same as a non-existing repository Signed-off-by: Johannes Löthberg johan...@kyriasis.com --- Changes since v1: * Fixed the namespace check, since I apparently

[PATCH/RFC] upload-pack: Fail if cloning empty namespace

Git should fail to clone if trying to clone from an non-existing ref namespace, since it's the same as a non-existing repository Signed-off-by: Johannes Löthberg johan...@kyriasis.com --- In version 4 of the ArchLinux User Repository, which is a hosting platform for recepies for building Arch

[PATCH v2] upload-pack: Fail if cloning empty namespace

Git should fail to clone if trying to clone from an non-existing ref namespace, since it's the same as a non-existing repository Signed-off-by: Johannes Löthberg johan...@kyriasis.com --- Changes since v1: * Fixed the namespace check, since I apparently forgot to check with a bare repo in my

Re: [PATCH v4] receive-pack: Create a HEAD ref for ref namespace

On 05/06, Johannes Löthberg wrote: Each ref namespace have their own separate branches, tags, and HEAD, so when pushing to a namespace we need to make sure that there exists a HEAD ref for the namespace, otherwise you will not be able to check out the repo after cloning from a namespace Signed

Re: [PATCH] receive-pack: Create a HEAD ref for ref namespace

Ping. -- Sincerely, Johannes Löthberg (Sent from my phone.)N�r��yb�X��ǧv�^�)޺{.n�+ا���ܨ}���Ơz�j:+v���zZ+��+zf���h���~i���z��w���?��)ߢf

Re: [PATCH] receive-pack: Create a HEAD ref for ref namespace

strbuf namespaced_head_buf = STRBUF_INIT;) Hmm, that's weird, no clue how that happened. Thanks. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature

[PATCH v2 2/2] t: Add test for cloning from ref namespace

Test that the master ref is set up properly when cloning from a ref namespace Signed-off-by: Johannes Löthberg johan...@kyriasis.com --- t/t9904-clone-from-ref-namespace.sh | 33 + 1 file changed, 33 insertions(+) create mode 100755 t/t9904-clone-from-ref

[PATCH v2 1/2] receive-pack: Create a HEAD ref for ref namespace

Each ref namespace have their own separate branches, tags, and HEAD, so when pushing to a namespace we need to make sure that there exists a HEAD ref for the namespace, otherwise you will not be able to check out the repo after cloning from a namespace Signed-off-by: Johannes Löthberg johan

[PATCH v2] Fix cloning from ref namespace

Since v1: * Added a test case Johannes Löthberg (2): receive-pack: Create a HEAD ref for ref namespace t: Add test for cloning from ref namespace builtin/receive-pack.c | 12 +++- t/t9904-clone-from-ref-namespace.sh | 33 + 2 files

Re: [PATCH] receive-pack: Create a HEAD ref for ref namespace

On 05/06, Michael J Gruber wrote: (Also, your patch duplicates the line struct strbuf namespaced_head_buf = STRBUF_INIT;) I replied too soon, it doesn't duplicate it, it's a different variable named similarly. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https

Re: [PATCH v2 2/2] t: Add test for cloning from ref namespace

On 05/06, Johannes Löthberg wrote: On 05/06, Junio C Hamano wrote: Johannes Löthberg johan...@kyriasis.com writes: git -C ../bare symbolic-ref HEAD actual echo refs/heads/master expect test_cmp expect actual git -C ../bare rev

[PATCH v4] receive-pack: Create a HEAD ref for ref namespace

Each ref namespace have their own separate branches, tags, and HEAD, so when pushing to a namespace we need to make sure that there exists a HEAD ref for the namespace, otherwise you will not be able to check out the repo after cloning from a namespace Signed-off-by: Johannes Löthberg johan

Re: [PATCH v3] receive-pack: Create a HEAD ref for ref namespace

On 05/06, Junio C Hamano wrote: Johannes Löthberg johan...@kyriasis.com writes: + + echo ref: refs/namespaces/new_namespace/refs/heads/master expect + test_cmp expect ../bare/refs/namespaces/new_namespace/HEAD Use symbolic-ref refs/namespaces/new_namespace

Re: [PATCH v2 2/2] t: Add test for cloning from ref namespace

On 05/06, Junio C Hamano wrote: Johannes Löthberg johan...@kyriasis.com writes: + It seems that 5509 already has a few tests for namespaced transfer in both directions. Perhaps this new test would fit there better? Missed that, will move it there. Also I

Re: [PATCH v2 2/2] t: Add test for cloning from ref namespace

On 05/06, Junio C Hamano wrote: Johannes Löthberg johan...@kyriasis.com writes: Hmm, it seems that git-rev-parse doesn't handle GIT_NAMESPACE yet, so can't check it for the namespaced push right now. Not sure if I can fix that myself though. I do not see a need for rev-parse to pay attention

[PATCH v3] receive-pack: Create a HEAD ref for ref namespace

Each ref namespace have their own separate branches, tags, and HEAD, so when pushing to a namespace we need to make sure that there exists a HEAD ref for the namespace, otherwise you will not be able to check out the repo after cloning from a namespace Signed-off-by: Johannes Löthberg johan

Re: [PATCH v3] receive-pack: Create a HEAD ref for ref namespace

I should also look into why the other tests in t5509 fail later. -- Sincerely, Johannes Löthberg PGP Key ID: 0x50FB9B273A9D0BB5 https://theos.kyriasis.com/~kyrias/ signature.asc Description: PGP signature

[PATCH] receive-pack: Create a HEAD ref for ref namespace

Each ref namespace have their own separate branches, tags, and HEAD, so when pushing to a namespace we need to make sure that there exists a HEAD ref for the namespace, otherwise you will not be able to check out the repo after cloning from a namespace --- So, I have absolutely no clue where this