From: mkoegler@auto.tuwien.ac.at (Martin Koegler)
To: git@vger.kernel.org
Subject: [RFC] Fsck while fetching
Date: Tue, 4 Mar 2008 08:55:45 +0100 [thread overview]
Message-ID: <20080304075545.GA31793@auto.tuwien.ac.at> (raw)
As the infrastructure for checking the objects and their connectivity
while pushing is in place, it is easy to do the same while fetching on
non shallow repositories.
On shallow repositories this is currently only possible, if the list
of shallow commits does not change (eg. no depth option).
The neccessary changes are:
* Read a config option in fetch-pack to disable it (default: true)
* Add in fetch-pack --strict to the command lines of index-pack and
unpack-objects, if the config option is true and args.depth is 0.
This leads to the question:
* How should the config option be named? fetch.fsckObjects? Should
receive.fsckObjects be reused? Should receive.fsckObjects be renamed
to a new name, which is used in both cases?
On additional question:
* fsck has a strict option, which looks for files with 0664 mode. How
should such files be handled with the checking while pushing/fetching:
ignored, rejected or config option for the behaviour?
mfg Martin Kögler
reply other threads:[~2008-03-04 7:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080304075545.GA31793@auto.tuwien.ac.at \
--to=mkoegler@auto.tuwien.ac.at \
--cc=git@vger.kernel.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).