discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Jan Stary <hans@stare.cz>
To: discuss@mdocml.bsd.lv
Cc: Hank Leininger <hlein@marc.info>, webguy@marc.info
Subject: Re: mandoc mailing list archives
Date: Sun, 5 Apr 2020 09:50:05 +0200	[thread overview]
Message-ID: <20200405075005.GA97152@www.stare.cz> (raw)
In-Reply-To: <20200405024100.GE27565@ultron.spinoli.org>

On Apr 04 20:41:00, hlein@marc.info wrote:
> On Sat, Apr 04, 2020 at 01:07:01PM -0600, Hank Leininger wrote:
> > 
> > Sure.  I've sent subscription requests, I'll activate the list once
> > those are complete.
> > 
> > I also pulled down the existing archives from inbox.vuxu.org, that's a
> > neat service/software that I don't think I've seen before. Making each
> > list message available as a git commit, that's pretty slick. I will need
> > to whip up a quick script to turn them back into an importable mbox, but
> > that'll be easy.
> 
> Done, they're now available:
> 
>   https://marc.info/?l=mandoc-discuss
>   https://marc.info/?l=mandoc-source
>   https://marc.info/?l=mandoc-tech
> 
> Thanks again to Leah Neukirchen for inbox.vuxu.org, which allowed me to
> fetch and import the existing archives easily.
> 
> I could not decide what existing list-group in MARC the mandoc lists
> ought to be categorized under, after thinking deeply about the question
> for about 20 seconds.  Do you have any suggestions?
> 
> Thanks,
> 
> Hank Leininger <hlein@marc.info>
> ED0E 3040 4240 1DD9 5B2E  6DEC A60B CB9D 0939 76F7


--
 To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv


       reply	other threads:[~2020-04-05  7:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200403143304.GA82249@www.stare.cz>
     [not found] ` <20200404190701.GD27565@ultron.spinoli.org>
     [not found]   ` <20200405024100.GE27565@ultron.spinoli.org>
2020-04-05  7:50     ` Jan Stary [this message]
2020-04-05 13:43       ` Ingo Schwarze

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=20200405075005.GA97152@www.stare.cz \
    --to=hans@stare.cz \
    --cc=discuss@mandoc.bsd.lv \
    --cc=discuss@mdocml.bsd.lv \
    --cc=hlein@marc.info \
    --cc=webguy@marc.info \
    /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).