From: Junio C Hamano <gitster@pobox.com>
To: Toon Claes <toon@iotcl.com>
Cc: git@vger.kernel.org
Subject: Re: Teach git-fetch(1) to use a quarantine directory
Date: Mon, 17 Jul 2023 16:56:05 -0700 [thread overview]
Message-ID: <xmqqcz0qdre2.fsf@gitster.g> (raw)
In-Reply-To: <87edl6bx7o.fsf@iotcl.com> (Toon Claes's message of "Mon, 17 Jul 2023 12:48:17 +0200")
Toon Claes <toon@iotcl.com> writes:
> 1) Does it even make sense to make use git-fetch(1) use a quarantine
> directory?
What's the goal here? If the push gets rejected, remove the
incoming packfile data together with quarantine repository? Who
will be doing such a rejection and how? Does something run in the
quarantine repository as its main repository while using the final
one as an alternate (presumably some form of hooks) to make that
decision? If these goals do not make sense, then no, it does not
make sense to teach "fetch" to use a quarantine directory.
Otherwise, teaching "fetch" would be a reasonable way to go forward.
It is a separate issue if the mechanisms added (if any) when we
tought receive-pack to use a quarantine repository are directly
applicable, if if they need some twaking, in order to reuse them in
the context of "git fetch". But their needing some tweaking does
not mean that it does not make sense to try teaching "fetch" to use
quarantine repository.
Thanks.
prev parent reply other threads:[~2023-07-17 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 10:48 Teach git-fetch(1) to use a quarantine directory Toon Claes
2023-07-17 14:06 ` Taylor Blau
2023-07-19 7:24 ` Patrick Steinhardt
2023-07-17 23:47 ` Jonathan Tan
2023-07-17 23:56 ` Junio C Hamano [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=xmqqcz0qdre2.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=toon@iotcl.com \
/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).