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, 07:42 UTC
Message-ID
<EC3AE084-0AB8-406A-A3C7-916CCF35BEAE@zib.de>
In-Reply-To
<0056A63A-D511-4FDD-82A6-A13B06E237E9@zib.de>
On May 9, 2007, at 1:59 AM, Steffen Prohaska wrote:
Show 9 quoted lines
> The old implementation executed 'cvs status' for each file touched  
> by the patch
> to be applied. The new code calls 'cvs status' only once and parses  
> cvs's
> output to collect status information of all files contained in the  
> cvs working
> copy.
>
> [...]

I didn't recognize that my modifications cause the testsuite to fail. I'll send a corrected patch in a minute.

I apologize,
- Steffen
Previous: Steffen ProhaskaNext: Steffen Prohaska
Message 2 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.