List for cgit developers and users
 help / color / mirror / Atom feed
From: katolaz at (KatolaZ)
Subject: a gopher version of cgit
Date: Thu, 2 Aug 2018 11:15:02 +0200	[thread overview]
Message-ID: <> (raw)

Dear cgitters,

just to let you know that I have been working on a mod/fork of cgit
with a Gopher (RCF 1436) interface, that I called "cgit-70". The repo
is available at:

and a demo with some repos can be accessed via Gopher at:


I have basically replaced HTML generation with Gopher stuff, and
simplified a bit the interface, since Gopher allows for just one
"link" (called "selector) per line. The plan for now is to keep it in
line with cgit, using as much as possible separate files (you will
notice the ui_70-*.c files in the tree).

Despite being mostly based on cgit, which is a rock-solid project, and
even if it already provides most of the basic cgit functionalities,
cgit-70 is still to be considered in alpha stage. I don't expect the
project to be of any relevance, but wanted to share it anyway, just in
case anybody here still uses or remembers Gopher, and wants to give it
a try :)

No need to say that comments, suggestions, critics, and feedback would
be very welcome.

Sorry for the noise, and thanks again to the cgit devs for the great
work they have done.



[ ~.,_  Enzo Nicosia aka KatolaZ - Devuan -- Freaknet Medialab  ]  
[     "+.  katolaz [at] --- katolaz [at]  ]
[       @) ---  Devuan GNU + Linux User  ]
[     @@) --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <>

             reply	other threads:[~2018-08-02  9:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02  9:15 katolaz [this message]
2018-08-03  4:18 ` Jason

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