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

Re: [PATCH] Fix typo in remote set-head usage

From
Junio C Hamano <gitster@pobox.com>
Date
Nov 26, 2012, 18:16 UTC
Message-ID
<7vwqx8rzzf.fsf@alter.siamese.dyndns.org>
In-Reply-To
<1353851019-27254-1-git-send-email-apelisse@gmail.com>
Antoine Pelisse <apelisse@gmail.com> writes:
Show 5 quoted lines
> parenthesis are not matching in `builtin_remote_sethead_usage`
> as a square bracket is closing something never opened.
> ---
> This will also break all translation files, should I also send a patch
> to update them ?

"git grep -A2 -e 'remote set-head <name>' po/" tells me that we already have both the correct variant and the broken one, and they are both translated ;-) so I do not think we have much to worry about the i18n fallout in this case, but thanks anyway for thinking about it.

You would need to sign off your patch, but otherwise looks good to me.

Thanks.
Show 22 quoted lines
>
> Cheers,
> Antoine Pelisse
>
>  builtin/remote.c |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/builtin/remote.c b/builtin/remote.c
> index a5a4b23..937484d 100644
> --- a/builtin/remote.c
> +++ b/builtin/remote.c
> @@ -39,7 +39,7 @@ static const char * const builtin_remote_rm_usage[] = {
>  };
>
>  static const char * const builtin_remote_sethead_usage[] = {
> -	N_("git remote set-head <name> (-a | -d | <branch>])"),
> +	N_("git remote set-head <name> (-a | -d | <branch>)"),
>  	NULL
>  };
>
> --
> 1.7.9.5
Previous: Antoine PelisseNext: Antoine Pelisse
Message 2 of 4 in “Fix typo in remote set-head usage”
  1. Fix typo in remote set-head usageAntoine Pelisse, Nov 25, 2012
  2. Junio C HamanoNov 26, 2012
  3. Fix typo in remote set-head usageAntoine Pelisse, Nov 26, 2012
  4. Junio C HamanoNov 26, 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.