From: Vegard Nossum <vegard.nossum@oracle.com>
To: cgit@lists.zx2c4.com
Cc: konstantin@linuxfoundation.org
Subject: git notes for the Linux kernel
Date: Mon, 17 Oct 2022 13:50:04 +0200 [thread overview]
Message-ID: <20221017115010.21977-1-vegard.nossum@oracle.com> (raw)
Hi cgit maintainers,
I've improved the support for git notes in cgit, including the ability
to load notes from a separate repository than the one you are viewing.
My use case is using a separate repository of git notes for the Linux
kernel to annotate commits with extra cross-referencing information such
as e.g.:
- lore links to patch submissions matching the patch,
- references to subsequent fixes (if the current commit is buggy)
- mitre links to CVEs
- references to backports in stable/LTS
My hope is that these notes can eventually be displayed on
git.kernel.org -- at least, we've found the notes invaluable and a huge
time saver in different types of kernel work. (I'm still in the process
of working out how to release these notes and/or the scripts generating
them, but that's a different topic.)
I tried to submit the git.git patches upstream, but they were rejected
by the maintainer for not being general enough:
https://lore.kernel.org/git/20220802075401.2393-1-vegard.nossum@oracle.com/
I will unfortunately not be able to implement the git maintainer's
suggestion, so I'll just offer up my git and cgit patches here, in case
cgit would still like this functionality; it would mean having to
maintain and carry the extra 2 git.git patches. I would be happy to
continue forward-porting those patches, however, as this is something I
will need to do for our internal use anyway.
Here is a screenshot of cgit with Linux kernel notes in action:
https://vegard.github.io/cgit/6399f1fae4ec.png
cgit patches will follow in replies to this email -- the two prerequisite
git.git patches are available at the git mailing list link above and
should apply cleanly to v2.38.0.
Thanks,
Vegard
next reply other threads:[~2022-10-17 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 11:50 Vegard Nossum [this message]
2022-10-17 11:50 ` [PATCH 1/6] Support notes from external repositories Vegard Nossum
2022-10-17 11:50 ` [PATCH 3/6] git: handle diff_queue_is_empty() changes Vegard Nossum
2022-10-17 11:50 ` [PATCH 4/6] git: handle string_list_init_{nodup, dup}() changes for ctx.cfg.mimetypes Vegard Nossum
2022-10-17 11:50 ` [PATCH 5/6] cgit: add extra alternates Vegard Nossum
2022-10-17 12:12 ` git notes for the Linux kernel Vegard Nossum
2022-10-18 20:20 ` John Keeping
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221017115010.21977-1-vegard.nossum@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=cgit@lists.zx2c4.com \
--cc=konstantin@linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).