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

Re: [PATCH 2/6] reflog: remove i18n legos in pruning message

From
Junio C Hamano <gitster@pobox.com>
Date
May 31, 2012, 17:56 UTC
Message-ID
<7vlik86xqd.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20120531134538.GA10523@burratino>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 8 quoted lines
> Thanks.  Style: how about
>
> 	if (!cb->newlog)
> 		printf("would prune %s", message);
> 	else if (cb->cmd->verbose)
> 		printf("prune %s", message);
>
> ?  I think that would be more readable than the lego original.
That is very much more preferred.
> BTW I'm not sure if this message would be a good candidate for
> translation.

These are for human consumption; they used to go to standard error stream back when it was written at 4264dc1 (git reflog expire, 2006-12-19).

Previous: Nguyen Thai Ngoc DuyNext: Jonathan Nieder
Message 10 of 17 in “i18n: apply: split to fix a partial i18n message”
  1. i18n: apply: split to fix a partial i18n messageJiang Xin, May 31, 2012
  2. Nguyễn Thái Ngọc DuyMay 31, 2012
  3. 1/6 Remove i18n legos in notifying new branch tracking setupNguyễn Thái Ngọc Duy, May 31, 2012
  4. Jonathan NiederMay 31, 2012
  5. 2/6 reflog: remove i18n legos in pruning messageNguyễn Thái Ngọc Duy, May 31, 2012
  6. Jonathan NiederMay 31, 2012
  7. Nguyen Thai Ngoc DuyMay 31, 2012
  8. Jonathan NiederMay 31, 2012
  9. Nguyen Thai Ngoc DuyMay 31, 2012
  10. Junio C HamanoMay 31, 2012
  11. Jonathan NiederMay 31, 2012
  12. 3/6 merge-recursive: remove i18n legos in conflict messagesNguyễn Thái Ngọc Duy, May 31, 2012
  13. Jonathan NiederMay 31, 2012
  14. Nguyen Thai Ngoc DuyMay 31, 2012
  15. 4/6 notes-merge: remove i18n legos in merge result messageNguyễn Thái Ngọc Duy, May 31, 2012
  16. 5/6 rerere: remove i18n legos in result messageNguyễn Thái Ngọc Duy, May 31, 2012
  17. 6/6 unpack-trees: remove i18n legos in unpack's porcelain error messagesNguyễn Thái Ngọc Duy, May 31, 2012

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.