List for cgit developers and users
 help / color / mirror / Atom feed
From: Vegard Nossum <>
Subject: Re: git notes for the Linux kernel
Date: Mon, 17 Oct 2022 14:12:27 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

[-- Attachment #1: Type: text/plain, Size: 595 bytes --]

On 10/17/22 13:50, Vegard Nossum wrote:
> 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.

Looks like the list rejected 2 of the patches for containing HTML, when
those were actually plaintext emails with patches tweaking cgit's HTML
generation code -- maybe something to look into, as that doesn't seem
too unusual for patches on this mailing list.

Anyway, also attaching a tarball with all the patches here, assuming
that makes it through the filter!


[-- Attachment #2: notes.tar.bz2 --]
[-- Type: application/x-bzip, Size: 4989 bytes --]

  parent reply	other threads:[~2022-10-17 12:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-17 11:50 Vegard Nossum
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 ` Vegard Nossum [this message]
2022-10-18 20:20 ` git notes for the Linux kernel 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).