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

Re: [PATCH] Repack should try to prevent itself from running twice, concurrently.

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Jun 25, 2006, 10:17 UTC
Message-ID
<Pine.LNX.4.63.0606251216250.29667@wbgn013.biozentrum.uni-wuerzburg.de>
In-Reply-To
<11512302144123-git-send-email-ryan@michonline.com>
Hi,
On Sun, 25 Jun 2006, Ryan Anderson wrote:
Show 8 quoted lines
> +if [ -f $GIT_DIR/repack.lock ]
> +then
> +	echo "Existing repack job appears to be running."
> +	echo "Remove $GIT_DIR/repack.lock if this is not the case."
> +	exit 1
> +else
> +	echo $$ > $GIT_DIR/repack.lock
> +fi

It is not like it is being an atomic operation, but then, we are not going to call repack multiple times a second. I'd say it is sufficient.

Ciao, Dscho

Previous: Ryan AndersonNext: Linus Torvalds
Message 4 of 7 in “[RFC] git-fetch - repack in the background after fetching”
  1. Martin LanghoffJun 24, 2006
  2. Junio C HamanoJun 25, 2006
  3. Repack should try to prevent itself from running twice, concurrently.Ryan Anderson, Jun 25, 2006
  4. Johannes SchindelinJun 25, 2006
  5. Linus TorvaldsJun 25, 2006
  6. Johannes SchindelinJun 25, 2006
  7. Linus TorvaldsJun 25, 2006

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.