All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: "Philip Oakley" <philipoakley@iee.org>,
	"Christian Couder" <christian.couder@gmail.com>,
	git <git@vger.kernel.org>,
	"Thomas Ferris Nicolaisen" <tfnico@gmail.com>,
	"Nicola Paolucci" <durden@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>, "Jeff King" <peff@peff.net>,
	"Nguyen Thai Ngoc Duy" <pclouds@gmail.com>,
	"Stefan Beller" <sbeller@google.com>,
	"Michael Haggerty" <mhagger@alum.mit.edu>,
	"Ramsay Jones" <ramsay@ramsayjones.plus.com>,
	"remi galan-alfonso" <remi.galan-alfonso@ensimag.grenoble-inp.fr>,
	"Johannes Sixt" <j6t@kdbg.org>,
	"Torsten Bögershausen" <tboegi@web.de>,
	"Josh Triplett" <josh@joshtriplett.org>,
	"Lars Schneider" <larsxschneider@gmail.com>,
	meta@public-inbox.org
Subject: Re: Draft of Git Rev News edition 18
Date: Tue, 16 Aug 2016 09:30:27 +0000	[thread overview]
Message-ID: <20160816093027.GA27347@dcvr> (raw)
In-Reply-To: <9f3b254f-451e-4f6d-233c-7e995d8e369e@gmail.com>

Jakub Narębski <jnareb@gmail.com> wrote:
> It's a great pity that https://public-inbox.org/ is just
> directory index, not a true home page.

+Cc meta@public-inbox.org

I'm not sure one could do better while staying true to the
minimalist nature of plain-text email.

In the spirit of decentralization, there may not be /a/
homepage, but many.   Everything is meant to clonable with each
public-inbox, so maybe every public-inbox will have a code
branch attached to it with the source+docs bundled.


At least for now, other pages are more easily discoverable[1]
but one day I hope to have repobrowse[2] running there (and
maybe everywhere).


For now, I am prioritizing user/admin/hacker documentation so
more instances can exist.  I'll probably get some online help
stuff up tomorrow.


[1] at least the top-level of public-inbox.org already has more
    content than both YHBT.net and bogomips.org combined :)

[2] git clone -b repobrowse https://public-inbox.org/ ...
    (idle the moment: think cgit|gitweb with the same (lack of)
     style as public-inbox, +search, +mail thread integration)

  parent reply	other threads:[~2016-08-16  9:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14 17:15 Draft of Git Rev News edition 18 Christian Couder
2016-08-14 20:58 ` Junio C Hamano
2016-08-15  6:17   ` Christian Couder
2016-08-14 21:10 ` Philip Oakley
2016-08-14 23:10   ` Eric Wong
2016-08-14 23:37     ` Philip Oakley
2016-08-14 23:57       ` Eric Wong
2016-08-18 10:03       ` Eric Wong
2016-08-15  6:16     ` Christian Couder
2016-08-15 18:08   ` Jakub Narębski
2016-08-15 18:25     ` Jakub Narębski
2016-08-16  9:30     ` Eric Wong [this message]
2016-08-16  9:34       ` Josh Triplett
2016-08-16 21:27         ` Eric Wong
2016-08-16 22:32           ` Josh Triplett
2016-09-07  1:08             ` Eric Wong
2016-08-16 12:27     ` Christian Couder

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=20160816093027.GA27347@dcvr \
    --to=e@80x24.org \
    --cc=christian.couder@gmail.com \
    --cc=durden@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=jnareb@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=larsxschneider@gmail.com \
    --cc=meta@public-inbox.org \
    --cc=mhagger@alum.mit.edu \
    --cc=pclouds@gmail.com \
    --cc=peff@peff.net \
    --cc=philipoakley@iee.org \
    --cc=ramsay@ramsayjones.plus.com \
    --cc=remi.galan-alfonso@ensimag.grenoble-inp.fr \
    --cc=sbeller@google.com \
    --cc=tboegi@web.de \
    --cc=tfnico@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.