user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Eric Wong <>
To: Alyssa Ross <>
Subject: Re: public-inbox-init with minimal info
Date: Wed, 16 Oct 2019 10:04:45 +0000	[thread overview]
Message-ID: <20191016100445.GA23983@dcvr> (raw)
In-Reply-To: <20191010081924.GA14812@ailurophile>

Eric Wong <> wrote:
> Alyssa Ross <> wrote:
> > Here's an idea for a lint: I lost most of a day wondering what I had
> > done wrong, before realising that I was setting mainrepo to all.git,
> > rather than its parent directory.  The name "mainrepo" isn't great, IMO,
> > but a lint could have accomodated for that.
> Sorry about wasting your time!  Yeah, "mainrepo" is a bad name,
> especially with v2 :<
> I guess we can shift to "inboxdir" and keep the old alias
> indefinitely for compatibility, since there's already INBOX_DIR
> all over the documentation.

Patches posted at:

(and I needed a 3/2 fixup after deploying :x)
Will merge to master soonish.  I think it's the last major thing
to do before 1.2.0 (and some more doc updates coming...)

      reply	other threads:[~2019-10-16 10:04 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-03 11:16 public-inbox-init with minimal info Alyssa Ross
2019-10-04  2:45 ` Eric Wong
2019-10-04 11:18   ` Alyssa Ross
2019-10-05  5:14     ` Eric Wong
2019-10-05 13:05       ` Alyssa Ross
2019-10-05 19:58         ` Eric Wong
2019-10-06  9:52           ` Alyssa Ross
2019-10-06 12:01             ` Eric Wong
2019-10-07 20:52               ` Alyssa Ross
2019-10-08  7:11                 ` Eric Wong
2019-10-09 12:09                   ` Alyssa Ross
2019-10-10  8:19                     ` Eric Wong
2019-10-16 10:04                       ` 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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191016100445.GA23983@dcvr \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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