From: Lars Schneider <larsxschneider@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: RFC: Enable delayed responses to Git clean/smudge filter requests
Date: Mon, 14 Nov 2016 22:09:56 +0100 [thread overview]
Message-ID: <D10F7C47-14E8-465B-8B7A-A09A1B28A39F@gmail.com> (raw)
Hi,
Git always performs a clean/smudge filter on files in sequential order.
Sometimes a filter operation can take a noticeable amount of time.
This blocks the entire Git process.
I would like to give a filter process the possibility to answer Git with
"I got your request, I am processing it, ask me for the result later!".
I see the following way to realize this:
In unpack-trees.c:check_updates() [1] we loop through the cache
entries and "ask me later" could be an acceptable return value of the
checkout_entry() call. The loop could run until all entries returned
success or error.
The filter machinery is triggered in various other places in Git and
all places that want to support "ask me later" would need to be patched
accordingly.
--
Do you think this could be a viable approach?
Do you see a better way?
Thanks,
Lars
[1] https://github.com/git/git/blob/3ab228137f980ff72dbdf5064a877d07bec76df9/unpack-trees.c#L267
next reply other threads:[~2016-11-14 21:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 21:09 Lars Schneider [this message]
2016-11-15 1:03 ` RFC: Enable delayed responses to Git clean/smudge filter requests Eric Wong
2016-11-15 14:29 ` Lars Schneider
2016-11-15 18:03 ` Junio C Hamano
2016-11-16 9:53 ` Lars Schneider
2016-11-16 18:15 ` Junio C Hamano
2016-11-16 18:47 ` Lars Schneider
2016-11-16 19:19 ` Junio C Hamano
2016-11-16 22:41 ` Jakub Narębski
2016-11-16 23:46 ` Junio C Hamano
2016-11-17 9:19 ` Lars Schneider
2016-11-24 15:45 ` Lars Schneider
2016-11-28 21:48 ` Junio C Hamano
2016-11-15 18:27 ` Eric Wong
2017-01-09 20:44 ` Stefan Beller
2017-01-11 12:57 ` Lars Schneider
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D10F7C47-14E8-465B-8B7A-A09A1B28A39F@gmail.com \
--to=larsxschneider@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).