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

Re: [PATCH 1/3] t3404: become resilient to GETTEXT_POISON

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Aug 17, 2016, 12:49 UTC
Message-ID
<alpine.DEB.2.20.1608171448060.4924@virtualbox>
In-Reply-To
<1471003142-1739-1-git-send-email-vascomalmeida@sapo.pt>
Hi Vasco,
On Fri, 12 Aug 2016, Vasco Almeida wrote:
> The concerned test greps the output of exit_with_patch() in
> git-rebase--interactive.sh script.
> 
> Signed-off-by: Vasco Almeida <vascomalmeida@sapo.pt>

Thank you for keeping an eye out for these issues. I have to admit that I am a bit confused when to use i18ngrep and when not, so it is good to know that my mistakes won't survive for long!

Ciao, Dscho

Previous: Vasco Almeida
Message 4 of 4 in “t3404: become resilient to GETTEXT_POISON”
  1. 1/3 t3404: become resilient to GETTEXT_POISONVasco Almeida, Aug 12, 2016
  2. 2/3 t5520: become resilient to GETTEXT_POISONVasco Almeida, Aug 12, 2016
  3. 3/3 t7411: become resilient to GETTEXT_POISONVasco Almeida, Aug 12, 2016
  4. Johannes SchindelinAug 17, 2016

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.