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

Re: [PATCH] Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file.

From
Steffen Prohaska <prohaska@zib.de>
Date
May 9, 2007, 13:00 UTC
Message-ID
<3467FF99-9945-4ECF-9282-308759E63ED9@zib.de>
In-Reply-To
<Pine.LNX.4.64.0705091424190.4167@racer.site>
On May 9, 2007, at 2:25 PM, Johannes Schindelin wrote:
Show 7 quoted lines
> What I was trying to get at: if you commit 900 files, and after the  
> 450th
> file somebody _else_ commits a file, which just so happens to be  
> one of
> your 450 remaining files, that safety check no longer holds.
>
> CVS is slow.

I know. I'd probably apply my patch late at night or on the weekend, when the chance is lower to conflict with other commits.

You can't remove the race conditions that you have when interacting with cvs. We can only decrease the chance of being hit by making the time window smaller. This is a side benefit of my patch. The main purpose is to lower the overall time needed to apply patch that modifies lots of files.

- Steffen
Previous: Johannes SchindelinNext: Robin Rosenberg
Message 7 of 15 in “Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file.”
  1. Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file.Steffen Prohaska, May 8, 2007
  2. Steffen ProhaskaMay 9, 2007
  3. Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file.Steffen Prohaska, May 9, 2007
  4. Johannes SchindelinMay 9, 2007
  5. Steffen ProhaskaMay 9, 2007
  6. Johannes SchindelinMay 9, 2007
  7. Steffen ProhaskaMay 9, 2007
  8. Robin RosenbergMay 9, 2007
  9. Steffen ProhaskaMay 9, 2007
  10. Optimized cvsexportcommit: calling 'cvs status' once instead of once per touched file.Steffen Prohaska, May 9, 2007
  11. Martin LanghoffMay 10, 2007
  12. Junio C HamanoMay 10, 2007
  13. RFH for [PATCH] Optimized cvsexportcommit: calling 'cvs status' only once instead of once per changed file.Junio C Hamano, May 13, 2007
  14. Robin RosenbergMay 13, 2007
  15. Martin LanghoffMay 14, 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.