From: Eric Wong <e@80x24.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: "Jakub Narębski" <jnareb@gmail.com>,
"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>,
"Lars Schneider" <larsxschneider@gmail.com>,
meta@public-inbox.org
Subject: Re: Draft of Git Rev News edition 18
Date: Wed, 7 Sep 2016 01:08:20 +0000 [thread overview]
Message-ID: <20160907010820.GA26951@dcvr> (raw)
In-Reply-To: <20160816223215.GC17195@cloud>
Josh Triplett <josh@joshtriplett.org> wrote:
> On Tue, Aug 16, 2016 at 09:27:04PM +0000, Eric Wong wrote:
> > As for other projects, I'm not aware of anybody else using it,
> > yet. I have some small projects using it, but most of those are
> > one-off throwaways and I'm not comfortable promoting those along
> > with public-inbox. I admit: I'm not comfortable promoting
> > anything I do, really.
>
> Please take this as encouragement to do so. I'd love to see the
> public-inbox equivalent to the main page of https://lists.debian.org/ ,
> as an example. (And I'd love to have public-inbox archives of Debian
> mailing lists.)
Just pushed out some POD (which should build to manpages),
so maybe early adopters can start hosting mirrors themselves(*).
https://public-inbox.org/meta/20160907004907.1479-1-e@80x24.org/
I hope public-inbox-overview(7) is a good starting point
(along with the existing INSTALL) and there'll be more docs
coming at some point...
Writing documentation tends to make my attention span drift all
over the place; so maybe parts don't make sense or were glossed
over, but I'll be glad to help clarify anything. (Responding
to emails is generally easier for me since I can answer things
specifically, tough to do for generic docs)
I'll try to get a tarball release out soonish,
but my schedule is unpredictable.
(*) None of the code has had any security audit, yet;
and there's no warranty of course.
prev parent reply other threads:[~2016-09-07 1:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP8UFD1iveotLsMOBnpa=hU4ohcQjZ-X7tjnzY4k+xz5KJvqBw@mail.gmail.com>
[not found] ` <D5A2E231FFE74D1C891A1653E1C2D797@PhilipOakley>
[not found] ` <9f3b254f-451e-4f6d-233c-7e995d8e369e@gmail.com>
2016-08-16 9:30 ` Draft of Git Rev News edition 18 Eric Wong
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 [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160907010820.GA26951@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).