From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] git/fetch problem in group writable repositories
Date: Sat, 17 Jul 2021 02:12:22 +0200 [thread overview]
Message-ID: <6ED103CF5E8296FBFD8D05A298F74959@felloff.net> (raw)
In-Reply-To: <83B133380A8B9F5599DFCF7B62249BD3@eigenstate.org>
> How does that interact with renaming? I want to keep the
> files around if the fetching and indexing succeed.
yeah, you'r right. that wont work.
--
cinap
next prev parent reply other threads:[~2021-07-17 0:21 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 [this message]
2021-07-17 0:11 ` Anthony Martin
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=6ED103CF5E8296FBFD8D05A298F74959@felloff.net \
--to=cinap_lenrek@felloff.net \
--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).