List for cgit developers and users
 help / color / mirror / Atom feed
From: actionmystique at (jean-christophe manciot)
Subject: [PATCH v2] Make default pages configurable
Date: Wed, 21 Aug 2019 16:50:06 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Applying 'Make default pages configurable' patch
git apply --verbose ../0001-Make-default-pages-configurable.patch
Checking patch cgit.c...
Checking patch cgit.h...
Checking patch cgitrc.5.txt...
Checking patch cmd.c...
Checking patch ui-repolist.c...
Checking patch ui-shared.c...
Hunk #2 succeeded at 1006 (offset 6 lines).
Hunk #3 succeeded at 1095 (offset 6 lines).
Checking patch ui-shared.h...
Applied patch cgit.c cleanly.
Applied patch cgit.h cleanly.
Applied patch cgitrc.5.txt cleanly.
Applied patch cmd.c cleanly.
Applied patch ui-repolist.c cleanly.
Applied patch ui-shared.c cleanly.
Applied patch ui-shared.h cleanly.

Nice work! I've tried the simple "default-page=about" setting in
/etc/cgitrc: it works beautifully.

On Tue, Aug 20, 2019 at 1:28 PM Na?m Favier <fnaim42 at> wrote:

> >  "Show original" displays an encrypted message
> That's curious, as no encryption was used on my end.
> > the patch from a non-gmail source after removing the non-original added
> new lines (as attached below) raises multiple issues, maybe because all
> tabulations have been replaced by spaces:
> Weird and weirder. As you can see on the pipermail archive
> (, the
> patch I sent uses tabs.
> Anyway, here's the original patch attached.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

      reply	other threads:[~2019-08-21 14:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 17:22 [PATCH] " 
2019-08-15 10:26 ` john
2019-08-15 10:56   ` 
2019-08-15 12:50   ` [PATCH v2] " 
2019-08-19  8:31     ` actionmystique
2019-08-19  9:44       ` 
2019-08-20  9:09         ` actionmystique
2019-08-20 11:28           ` 
2019-08-21 14:50             ` actionmystique [this message]

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