user/dev discussion of public-inbox itself
 help / color / mirror / code / Atom feed
From: Kyle Meyer <>
To: Eric Wong <>
Subject: Re: [PATCH] inbox: do not vivify {-repo_objs} during cleanup
Date: Tue, 28 Sep 2021 20:55:31 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <20210929001428.GA28946@dcvr>

Eric Wong writes:

> Thanks, the following should fix it (though I suppose @INC paths
> should be cleaned in WWW):
> ------8<-----
> Subject: [PATCH] inbox: do not vivify {-repo_objs} during cleanup

Seems to do the trick.  Thank you!

      reply	other threads:[~2021-09-29  0:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 23:21 solver: 'BUG {try_gits} empty' error Kyle Meyer
2021-09-29  0:14 ` [PATCH] inbox: do not vivify {-repo_objs} during cleanup Eric Wong
2021-09-29  0:55   ` Kyle Meyer [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 \ \ \ \ \

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