git/list[1] front-page[2] threads[3] people[4] search[5] about
 

inotify-commit, was Re: git guidance

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 28, 2009, 12:30 UTC
Message-ID
<alpine.DEB.1.00.0908281424100.7434@intel-tinevez-2-302>
In-Reply-To
<20071207220025.GD2001@atjola.homenet>
Hi,
[long Cc: list culled, as they probably forgot about this thread]
On Fri, 7 Dec 2007, Björn Steinbrink wrote:
Show 18 quoted lines
> That said, out of pure curiousness I came up with the attached script 
> which just uses inotifywait to watch a directory and issue git commands 
> on certain events. It is extremely stupid, but seems to work. And at 
> least it hasn't got the drawbacks of a real gitfs regarding the need to 
> have a "separate" non-versioned storage area for the working directory, 
> because it simply uses the existing working directory wherever that 
> might be stored. It doesn't use GIT_DIR/WORK_DIR yet, but hey, should be 
> easy to add...
> 
> Feel free to mess with that thing, hey, maybe you even like it and
> extend it to match your proposed workflow even more. I for sure won't
> use or even extend it, so you're likely on your own there.
> 
> Side-note: Writing that script probably took less time than writing this
> email and probably less time than was wasted on this topic. Makes me
> want to use today's preferred "Code talks, b...s... walks" statement,
> but I'll refrain from that... Just because I lack the credibility to say
> that, and the script attached is quite crappy ;-)
I could not agree more with the statement.

As it happens, I have a very delicate setup that we tested in a test environment as much as possible, but now we have to deploy it and I want to be able to rewind very quickly to a known-good state.

So I adjusted your script a little.  It now reads like this:

-- snip -- #!/bin/sh

# Originally by Bjoern Steinbrink, simplified by Johannes Schindelin
inotifywait -m -r --exclude ^\./\.git/.* \
        -e close_write -e move -e create -e delete . 2>/dev/null |
while read FILE_PATH EVENT FILE_NAME
do
        FILE_NAME="$FILE_PATH$FILE_NAME"
        FILE_NAME=${FILE_NAME#./}
        # git doesn't care about directories
        test -d "$FILE_NAME" && continue
        case "$EVENT" in
        *MOVED_TO*|*CREATE*)
                git add "$FILE_NAME"
                git commit -m "$FILE_NAME created"
                ;;
        *CLOSE_WRITE*|*MODIFY*)
                git add "$FILE_NAME"
                git commit -m "$FILE_NAME changed"
                ;;
        *DELETE*|*MOVED_FROM*)
                git rm --cached "$FILE_NAME"
                git commit -m "$FILE_NAME removed"
                ;;
        esac
done
-- snap --
Thanks for your original script!

Ciao, Dscho

Previous: Björn SteinbrinkNext: Phillip Susi
Message 23 of 25 in “Re: git guidance”
  1. Jing XueNov 29, 2007
  2. Linus TorvaldsNov 29, 2007
  3. Al BoldiDec 1, 2007
  4. Phillip SusiDec 4, 2007
  5. Al BoldiDec 7, 2007
  6. Andreas EricssonDec 6, 2007
  7. Al BoldiDec 7, 2007
  8. Johannes SchindelinDec 6, 2007
  9. Al BoldiDec 7, 2007
  10. Andreas EricssonDec 7, 2007
  11. Al BoldiDec 7, 2007
  12. Jakub NarebskiDec 7, 2007
  13. Al BoldiDec 7, 2007
  14. valdis.kletnieks@vt.eduDec 7, 2007
  15. Luke LuDec 7, 2007
  16. Al BoldiDec 8, 2007
  17. valdis.kletnieks@vt.eduDec 8, 2007
  18. Al BoldiDec 8, 2007
  19. Johannes SchindelinDec 8, 2007
  20. Andreas EricssonDec 7, 2007
  21. david@lang.hmDec 7, 2007
  22. Björn SteinbrinkDec 7, 2007
  23. inotify-commit, was Re: git guidanceJohannes Schindelin, Aug 28, 2009
  24. Phillip SusiDec 6, 2007
  25. Martin LanghoffDec 8, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.