From: Philip Oakley <philipoakley@iee.email>
To: Drew Noakes <drew@drewnoakes.com>, git@vger.kernel.org
Subject: Re: Detecting when bulk file-system operations complete
Date: Wed, 31 Mar 2021 17:03:21 +0100 [thread overview]
Message-ID: <5a1abc6b-52a3-fc12-166f-8af5e7bdff48@iee.email> (raw)
In-Reply-To: <CAJd66x6XT7m5Njg2kRyGJ80rU6WNcLifijS98=onJeBz+74rrA@mail.gmail.com>
Hi Drew,
On 31/03/2021 04:39, Drew Noakes wrote:
> Hi,
>
> I develop IDE tooling that watches a repo's workspace and reacts to changes.
>
> Bulk file-system changes (i.e. branch switch, rebase, merge,
> cherry-pick) trigger lots of file system events, and my tooling should
> ignore intermediary updates. Currently I debounce events with a fixed
> time span, but would like a more reliable and performant approach to
> scheduling this reactive work.
>
> Can this be done by monitoring the GITDIR in some way? For example, is
> there a file that's present when these operations are in flight, and
> which is removed when they complete?
>
> If an operation is interrupted (i.e. merge or rebase that hits a
> conflict) my tooling should consider the bulk operation as complete.
> This means that detecting a git-rebase-todo file or
> rebase-merge/rebase-apply folder is not adequate.
>
> Any help appreciated. Thanks!
>
> Drew.
You may want to look at the various bits of work on `fsmonitor` etc on
the mailing list archive
https://lore.kernel.org/git/?q=fsmonitor
to ensure that all the different approaches inter-operate with
reasonable efficiency..
--
Philip
next prev parent reply other threads:[~2021-03-31 16:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 3:39 Detecting when bulk file-system operations complete Drew Noakes
2021-03-31 16:03 ` Philip Oakley [this message]
2021-04-01 13:10 ` Derrick Stolee
2021-04-02 15:02 ` Jeff Hostetler
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=5a1abc6b-52a3-fc12-166f-8af5e7bdff48@iee.email \
--to=philipoakley@iee.email \
--cc=drew@drewnoakes.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.