On 03/20/18 14:24, Luis R. Rodriguez wrote: > *Iff* this seems sensible, this would only mean kernel.org would have to start > accepting git notes long term, for those who optionally want to push them or > fetch them. We don't disallow them. You just need to make sure you're fetching and pushing them, because they aren't by default. You can set this in your kernel.org origin section of .git/config: [remote origin] ... fetch = +refs/notes/*:refs/notes/* And then push them separately as "git push origin refs/notes/*". Since frontends clone with --mirror, the notes will be available on all git.kernel.org nodes (e.g. see https://git.kernel.org/mricon/hook-test/c/a8d310d4c13) If you do start using notes, I strongly suggest you pick a dedicated refspace for it instead of putting things into the default refs/notes/commits, e.g.: git notes --ref crosstree [...] This will create refs/notes/crosstree that has less of a chance to be clobbered by someone else's use of notes. Best, -- Konstantin Ryabitsev Director, IT Infrastructure Security The Linux Foundation
Attachment:
signature.asc
Description: OpenPGP digital signature
