From: Anthony Martin <ality@pbrane.org>
To: 9front@9front.org
Subject: Re: [9front] git/fetch problem in group writable repositories
Date: Fri, 16 Jul 2021 17:11:16 -0700 [thread overview]
Message-ID: <YPIgJBxT5r2DoqEF@alice> (raw)
In-Reply-To: <FD596DAD14918BA2B2BFB30BA4636BBF@felloff.net>
Looks good to me too.
cinap_lenrek@felloff.net once said:
> but why not ORCLOSE?
The only reason I didn't suggest ORCLOSE was because
I thought it might be useful to have the pack file
linger around for debugging a failed fetch.
Cheers,
Anthony
prev parent reply other threads:[~2021-07-17 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 5:49 Anthony Martin
2021-07-16 16:05 ` ori
2021-07-16 18:44 ` cinap_lenrek
2021-07-16 19:36 ` ori
2021-07-17 0:12 ` cinap_lenrek
2021-07-17 0:11 ` Anthony Martin [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YPIgJBxT5r2DoqEF@alice \
--to=ality@pbrane.org \
--cc=9front@9front.org \
/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).