List for cgit developers and users
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: "Matěj Cepl" <mcepl@cepl.eu>
Cc: <cgit@lists.zx2c4.com>
Subject: Re: Different page default for a repository
Date: Tue, 30 Jan 2024 12:47:10 +0100	[thread overview]
Message-ID: <20240130124710.1b2526c9@leda.eworm.net> (raw)
In-Reply-To: <CYRZUXBVVNSL.1XYG611ZP2N0B@cepl.eu>

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

Matěj Cepl <mcepl@cepl.eu> on Tue, 2024/01/30 12:11:
> On Tue Jan 30, 2024 at 11:43 AM CET, Matěj Cepl wrote:
> > On Tue Jan 30, 2024 at 9:05 AM CET, Christian Hesse wrote:  
> > > There's a patch available:
> > > https://git.zx2c4.com/cgit/log/?h=ch/default-pages
> > >
> > > But is has not been merged to the master branch.  
> >
> > Cgit however isn’t completely dead, is it (looking at the log,
> > there seems to be still some life in it)? So, what’s keeping this
> > patch from being merged? Is it so bad, dangerous?  
> 
> Oh silly me, the patch is old, but you have just published
> it. Sorry for being hasty!

Yes, it is old, and it has been there for a long time. I did just rebase it
right now.

These days Jason is not very active reviewing, merging & co...
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2024-01-30 11:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29 22:43 Matěj Cepl
2024-01-30  8:05 ` Christian Hesse
2024-01-30 10:43   ` Matěj Cepl
2024-01-30 11:11     ` Matěj Cepl
2024-01-30 11:47       ` Christian Hesse [this message]
2024-01-30 15:13         ` Matěj Cepl
2024-01-30 10:43   ` Matěj Cepl

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=20240130124710.1b2526c9@leda.eworm.net \
    --to=list@eworm.de \
    --cc=cgit@lists.zx2c4.com \
    --cc=mcepl@cepl.eu \
    /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).