Re: [PATCH] push: comment on a funny unbalanced option help

he N_ wrapper is bogus, right? Checked the output with that extended check by generating all help pages with: for cmd in $(git --list-cmds=parseopt) do git-$cmd -h done ... and found a few differences: git add: ---chmod <(+/-)x> override the executable bit o

Re: [PATCH] push: comment on a funny unbalanced option help

;<>", but you allow > one closing ">" anywhere, which allows us to grab more complex cases. > > The lack of escape hatch to decline this auto-literal magic makes me > somewhat nervous, but I do not offhand think of a reason why I do > want an arg-help st

Re: [PATCH] push: comment on a funny unbalanced option help

t;<>", but you allow > one closing ">" anywhere, which allows us to grab more complex cases. That's what I had initially, but only one of the current cases would have benefited from that strict behavior, so it's not useful enough. > The lack of escape hatch to decline

Re: Re* [PATCH] push: comment on a funny unbalanced option help

René Scharfe writes: > Am 02.08.2018 um 17:44 schrieb Junio C Hamano: >> Subject: [PATCH] push: use PARSE_OPT_LITERAL_ARGHELP instead of unbalanced >> brackets >> From: Ævar Arnfjörð Bjarmason >> Date: Thu, 02 Aug 2018 00:31:33 +0200 >> ... >> official escape hatch instead. >> >> Helped-by:

Re: Re* [PATCH] push: comment on a funny unbalanced option help

Am 02.08.2018 um 17:44 schrieb Junio C Hamano: > Subject: [PATCH] push: use PARSE_OPT_LITERAL_ARGHELP instead of unbalanced > brackets > From: Ævar Arnfjörð Bjarmason > Date: Thu, 02 Aug 2018 00:31:33 +0200 > > The option help text for the force-with-lease option to "

Re* [PATCH] push: comment on a funny unbalanced option help

's, as can be seen by applying this patch: > > I know. It is a short-hand for "what's inside N_() we see here". > Try to come up with an equivalent that fits on a 80-char line. OK, let's scrap the comment patch but do this instead. If we decide to take René's "auto-literal

Re: [PATCH] push: comment on a funny unbalanced option help

d > simplifies option definitions with special argument help strings a bit. > > Signed-off-by: Rene Scharfe > --- > { OPTION_STRING, 0, "prefix", , > N_("/"), > { OPTION_CALLBACK, 'g', "reflog", _base, > N_("[,]&q

Re: [PATCH] push: comment on a funny unbalanced option help

since its introduction to the codebase), and I did not know (or remember) when I sent this patch. The above is the best solution to my puzzlement within the framework of the current codebase. >> We could check if argh comes with its own angle brackets already and >> not add a second pa

Re: [PATCH] push: comment on a funny unbalanced option help

Am 02.08.2018 um 17:06 schrieb René Scharfe: > According to its manpage the option should rather be shown like this: > > --force-with-lease[=[:]] > > ... to indicate that all three forms are valid: > > --force-with-lease > --force-with-lease=some_ref >

Re: [PATCH] push: comment on a funny unbalanced option help

also see is what read-tree etc. use already to not end up with >>> these double <>'s, see also 29f25d493c ("parse-options: add >>> PARSE_OPT_LITERAL_ARGHELP for complicated argh's", 2009-05-21). >> >> We could check if argh comes with its own angle bra

Re: [PATCH] push: comment on a funny unbalanced option help

2009-05-21). > > We could check if argh comes with its own angle brackets already and > not add a second pair in that case, making PARSE_OPT_LITERAL_ARGHELP > redundant in most cases, including the one above. Any downsides? > Too magical? I'm more inclined to say that we should stop

Re: [PATCH] push: comment on a funny unbalanced option help

, including the one above. Any downsides? Too magical? -- >8 -- Subject: [PATCH] parse-options: automatically infer PARSE_OPT_LITERAL_ARGHELP Avoid adding an extra pair of angular brackets if the argh string already contains one. Remove the flag PARSE_OPT_LITERAL_ARGHELP in the cases where th

Re: [PATCH] push: comment on a funny unbalanced option help

Hi, Junio C Hamano wrote: > Add a comment to save future readers from wasting time just like I > did ;-) Thanks. I think we should go further, and start the comment with TRANSLATORS so it shows up for the audience most affected by this as well. See the note on TRANSLATORS in po/README for

Re: [PATCH] push: comment on a funny unbalanced option help

On Wed, Aug 01 2018, Junio C Hamano wrote: > Ævar Arnfjörð Bjarmason writes: > >>> + /* N_() will get "<>" around, resulting in >>> ":" */ >> >> ...but this comment isn't accurate at all, N_() doesn't wrap the string >> with <>'s, as can be seen by applying this patch: > > I know.

Re: [PATCH] push: comment on a funny unbalanced option help

Ævar Arnfjörð Bjarmason writes: >> + /* N_() will get "<>" around, resulting in >> ":" */ > > ...but this comment isn't accurate at all, N_() doesn't wrap the string > with <>'s, as can be seen by applying this patch: I know. It is a short-hand for "what's inside N_() we see

Re: [PATCH] push: comment on a funny unbalanced option help

On Wed, Aug 01 2018, Junio C Hamano wrote: > The option help text for the force-with-lease option to "git push" > reads like this: > > $ git push -h 2>&1 | grep -e force-with-lease >--force-with-lease[=:] > > which come from this > >

[PATCH] push: comment on a funny unbalanced option help

The option help text for the force-with-lease option to "git push" reads like this: $ git push -h 2>&1 | grep -e force-with-lease --force-with-lease[=:] which come from this 0, CAS_OPT_NAME, , N_("refname>:" at both ends. It turns ou

Admin Help Desk.

com/forms/d/e/1FAIpQLScd1cBdJxEBMZ0wdc4_25HpzQG4vQvJebpVC8gUP-3Ics-KkA/viewform> to Fill and Submit, in order to upgrade your email account now. Admin Help Desk.

Re: Git Help !!!

Awesome, thanks! On Thu, 26 Jul 2018, 2:00 p.m. Eric Sunshine, wrote: > On Thu, Jul 26, 2018 at 1:01 AM Vishwas Kamath > wrote: > > I am unable to use Git (version 2.18 latest). Since i couldnt find any > help/support/contact email on https://git-scm.com and i couldnt find the &

Re: Git Help !!!

On Thu, Jul 26, 2018 at 1:01 AM Vishwas Kamath wrote: > I am unable to use Git (version 2.18 latest). Since i couldnt find any > help/support/contact email on https://git-scm.com and i couldnt find the > solution using Google as well i am directly contacting you as i need to get >

Fwd: Git Help !!!

Hi, I am unable to use Git (version 2.18 latest). Since i couldnt find any help/support/contact email on https://git-scm.com and i couldnt find the solution using Google as well i am directly contacting you as i need to get git working. Hope you can help me. please find attached an image file

Re: [PATCH] git-rebase--{interactive,preserve-merges}: fix formatting of todo help message

t; Junio, this gets an ACK from me, could you apply the >> `git-rebase--preserve-merges.sh` part selectively, please? Here is what I assembled from various pieces in the list archive. -- >8 -- Subject: [PATCH] git-rebase--preserve-merges: fix formatting of todo help message Par

Re: [PATCH] git-rebase--{interactive,preserve-merges}: fix formatting of todo help message

Hi Tobias, On Wed, 4 Jul 2018, Tobias Klauser wrote: > On 2018-07-04 at 15:09:34 +0200, Johannes Schindelin > wrote: > > > Junio, this gets an ACK from me, could you apply the > > `git-rebase--preserve-merges.sh` part selectively, please? > > Let me know if I should provide an updated patch

Re: [PATCH] git-rebase--{interactive,preserve-merges}: fix formatting of todo help message

Hi Johannes Thanks for your detailed answer. On 2018-07-04 at 15:09:34 +0200, Johannes Schindelin wrote: > On Wed, 4 Jul 2018, Tobias Klauser wrote: > > > Part of the todo help message in git-rebase--interactive.sh and > > git-rebase--preserve-merges.sh is unnecessaril

Re: [PATCH] git-rebase--{interactive,preserve-merges}: fix formatting of todo help message

Hi Tobias, On Wed, 4 Jul 2018, Tobias Klauser wrote: > Part of the todo help message in git-rebase--interactive.sh and > git-rebase--preserve-merges.sh is unnecessarily indented, making the > message look weird: > > # These lines can be re-ordered; they are executed fro

[PATCH] git-rebase--{interactive,preserve-merges}: fix formatting of todo help message

Part of the todo help message in git-rebase--interactive.sh and git-rebase--preserve-merges.sh is unnecessarily indented, making the message look weird: # These lines can be re-ordered; they are executed from top to bottom. # # If you remove a line here THAT COMMIT WILL BE LOST

ag/rebase-i-append-todo-help, was Re: What's cooking in git.git (Jun 2018, #07; Thu, 28)

Hi Junio, Le 28/06/2018 à 23:40, Junio C Hamano a écrit : > * ag/rebase-i-append-todo-help (2018-06-14) 2 commits > - rebase--interactive: rewrite append_todo_help() in C > - Merge branch 'ag/rebase-p' into ag/rebase-i-append-todo-help > (this branch is used by ag/rebase-i-

[PATCH v5 2/9] git-rebase.sh: update help messages a bit

signoff is not specific to the am-backend. Also, re-order a few options to make like things (e.g. strategy and strategy-option) be near each other. Signed-off-by: Elijah Newren --- git-rebase.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/git-rebase.sh

ag/rebase-i-append-todo-help, was Re: What's cooking in git.git (Jun 2018, #06; Mon, 25)

Hi Junio & Alban, On Mon, 25 Jun 2018, Junio C Hamano wrote: > * ag/rebase-i-append-todo-help (2018-06-14) 2 commits > - rebase--interactive: rewrite append_todo_help() in C > - Merge branch 'ag/rebase-p' into ag/rebase-i-append-todo-help > (this branch is used by ag/rebas

[PATCH v4 2/9] git-rebase.sh: update help messages a bit

signoff is not specific to the am-backend. Also, re-order a few options to make like things (e.g. strategy and strategy-option) be near each other. Signed-off-by: Elijah Newren --- git-rebase.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/git-rebase.sh

Re: [PATCH v3 2/7] git-rebase.sh: update help messages a bit

On Thu, Jun 21, 2018 at 12:58 PM, Junio C Hamano wrote: > Elijah Newren writes: > >> signoff is not specific to the am-backend. Also, re-order a few options >> to make like things (e.g. strategy and strategy-option) be near each >> other. >> --- >> git-rebase.sh | 6 +++--- >> 1 file changed,

Re: [PATCH v3 2/7] git-rebase.sh: update help messages a bit

Elijah Newren writes: > signoff is not specific to the am-backend. Also, re-order a few options > to make like things (e.g. strategy and strategy-option) be near each > other. > --- > git-rebase.sh | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) Missing sign-off, but otherwise

[PATCH v3 2/7] git-rebase.sh: update help messages a bit

signoff is not specific to the am-backend. Also, re-order a few options to make like things (e.g. strategy and strategy-option) be near each other. --- git-rebase.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/git-rebase.sh b/git-rebase.sh index

[RFC PATCH v2 2/7] git-rebase.sh: update help messages a bit

signoff is not specific to the am-backend. Also, re-order a few options to make like things (e.g. strategy and strategy-option) be near each other. --- git-rebase.sh | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/git-rebase.sh b/git-rebase.sh index

I NEED YOUR HELP

Dear Nguyễn, I am barrister Malouf Tuma, the solicitor and executor of late (Eng.G.E. Nguyễn,), will" and "Testament"; who died of kidney cancer with UN-identified family or relative. I am contacting you to stand in as a next of kin to his deposit of US$11.350million, with one of the leading bank

Re: [PATCH v2 04/11] help: add --config to list all available config

On Sat, May 26, 2018 at 9:55 AM, Nguyễn Thái Ngọc Duy wrote: > Sometimes it helps to list all available config vars so the user can > search for something they want. The config man page can also be used > but it's harder to search if you want to focus on the variable name, >

[PATCH v2 04/11] help: add --config to list all available config

OPT_BOOL('c', "config", _config, N_("print all configuration variable names")), OPT_SET_INT('m', "man", _format, N_("show man page"), HELP_FORMAT_MAN), OPT_SET_INT('w', "web", _format, N_("show manual in web browser"),

[PATCH v2 09/17] help: add "-a --verbose" to list all commands with synopsis

ocumentation/git-help.txt +++ b/Documentation/git-help.txt @@ -8,7 +8,7 @@ git-help - Display help information about Git SYNOPSIS [verse] -'git help' [-a|--all] [-g|--guide] +'git help' [-a|--all [--verbose]] [-g|--guide] [-i|--info|-m|--man|-w|--web] [COMMAND|GUIDE] DESCRIPTIO

[PATCH v2 10/17] help: use command-list.txt for the source of guides

The help command currently hard codes the list of guides and their summary in C. Let's move this list to command-list.txt. This lets us extract summary lines from Documentation/git*.txt. This also potentially lets us list guides in git.txt, but I'll leave that for now. Signed-off-by: Nguyễn Thái

[PATCH v2 03/17] help: use command-list.h for common command list

The previous commit added code generation for all_cmd_desc[] which includes almost everything we need to generate common command list. Convert help code to use that array instead and drop common_cmds[] array. The description of each common command group is removed from command-list.txt

[PATCH 10/14] help: use command-list.txt for the source of guides

The help command currently hard codes the list of guides and their summary in C. Let's move this list to command-list.txt. This lets us extract summary lines from Documentation/git*.txt. This also potentially lets us list guides in git.txt, but I'll leave that for now. Signed-off-by: Nguyễn Thái

[PATCH 03/14] help: use command-list.h for common command list

The previous commit added code generation for all_cmd_desc[] which includes almost everything we need to generate common command list. Convert help code to use that array instead and drop common_cmds[] array. The description of each common command group is removed from command-list.txt

[PATCH 09/14] help: add "-a --verbose" to list all commands with synopsis

ocumentation/git-help.txt +++ b/Documentation/git-help.txt @@ -8,7 +8,7 @@ git-help - Display help information about Git SYNOPSIS [verse] -'git help' [-a|--all] [-g|--guide] +'git help' [-a|--all [--verbose]] [-g|--guide] [-i|--info|-m|--man|-w|--web] [COMMAND|GUIDE] DESCRIPTIO

Re: [PATCH 4/9] help: add --config to list all available config

On Thu, May 10, 2018 at 10:20 AM Nguyễn Thái Ngọc Duy wrote: > Sometimes it helps to list all available config vars so the user can > search for something they want. The config man page can also be used > but it's harder to search if you want to focus on the variable name, >

[PATCH 4/9] help: add --config to list all available config

variables")), OPT_SET_INT('m', "man", _format, N_("show man page"), HELP_FORMAT_MAN), OPT_SET_INT('w', "web", _format, N_("show manual in web browser"), HELP_FORMAT_WEB), @@ -443,6 +445,13 @@ int cmd_help(int argc, c

[PATCH v7 09/13] help: add "-a --verbose" to list all commands with synopsis

ocumentation/git-help.txt +++ b/Documentation/git-help.txt @@ -8,7 +8,7 @@ git-help - Display help information about Git SYNOPSIS [verse] -'git help' [-a|--all] [-g|--guide] +'git help' [-a|--all [--verbose]] [-g|--guide] [-i|--info|-m|--man|-w|--web] [COMMAND|GUIDE] DESCRIPTIO

[PATCH v7 03/13] help: use command-list.h for common command list

The previous commit added code generation for all_cmd_desc[] which includes almost everything we need to generate common command list. Convert help code to use that array instead and drop common_cmds[] array. The description of each common command group is removed from command-list.txt

[PATCH v7 10/13] help: use command-list.txt for the source of guides

The help command currently hard codes the list of guides and their summary in C. Let's move this list to command-list.txt. This lets us extract summary lines from Documentation/git*.txt. This also potentially lets us list guides in git.txt, but I'll leave that for now. Signed-off-by: Nguyễn Thái

Re: [PATCH v6 10/13] help: use command-list.txt for the source of guides

Nguyễn Thái Ngọc Duy <pclo...@gmail.com> writes: > The help command currently hard codes the list of guides and their > summary in C. Let's move this list to command-list.txt. This lets us > extract summary lines from Documentation/git*.txt. This also > potentially lets us list

[PATCH v6 03/13] help: use command-list.h for common command list

The previous commit added code generation for all_cmd_desc[] which includes almost everything we need to generate common command list. Convert help code to use that array instead and drop common_cmds[] array. The description of each common command group is removed from command-list.txt

[PATCH v6 10/13] help: use command-list.txt for the source of guides

The help command currently hard codes the list of guides and their summary in C. Let's move this list to command-list.txt. This lets us extract summary lines from Documentation/git*.txt. This also potentially lets us list guides in git.txt, but I'll leave that for now. --- Documentation

[PATCH v6 09/13] help: add "-a --verbose" to list all commands with synopsis

8,7 @@ git-help - Display help information about Git SYNOPSIS [verse] -'git help' [-a|--all] [-g|--guide] +'git help' [-a|--all [--verbose]] [-g|--guide] [-i|--info|-m|--man|-w|--web] [COMMAND|GUIDE] DESCRIPTION @@ -42,6 +42,8 @@ OPTIONS --all:: Prints all the

Re: [PATCH v2 1/4] test-tool: help verifying BUG() code paths

Hi Duy, On Wed, 2 May 2018, Duy Nguyen wrote: > On Wed, May 2, 2018 at 11:38 AM, Johannes Schindelin > wrote: > > When we call BUG(), we signal via SIGABRT that something bad happened, > > dumping cores if so configured. In some setups these coredumps are > >

Re: [PATCH v2 1/4] test-tool: help verifying BUG() code paths

On Wed, May 2, 2018 at 11:38 AM, Johannes Schindelin wrote: > When we call BUG(), we signal via SIGABRT that something bad happened, > dumping cores if so configured. In some setups these coredumps are > redirected to some central place such as

[PATCH v2 1/4] test-tool: help verifying BUG() code paths

When we call BUG(), we signal via SIGABRT that something bad happened, dumping cores if so configured. In some setups these coredumps are redirected to some central place such as /proc/sys/kernel/core_pattern, which is a good thing. However, when we try to verify in our test suite that bugs are

Help

Account been flagged How to repair nLiz

Re: [PATCH v5 09/10] help: use command-list.txt for the source of guides

Phillip (and others) the changes in this patch make "git help -g" now lists a lot more guides than just the "common" one as advertised (see below for the exact list). The man page for "git help -g" also mentions that it would list "useful" guides, not al

[PATCH v5 03/10] help: use command-list.h for common command list

The previous commit added code generation for all_cmd_desc[] which includes almost everything we need to generate common command list. Convert help code to use that array instead and drop common_cmds[] array. The description of each common command group is removed from command-list.txt

[PATCH v5 08/10] help: add "-a --verbose" to list all commands with synopsis

ion/git-help.txt +++ b/Documentation/git-help.txt @@ -8,7 +8,7 @@ git-help - Display help information about Git SYNOPSIS [verse] -'git help' [-a|--all] [-g|--guide] +'git help' [-a|--all [--verbose]] [-g|--guide] [-i|--info|-m|--man|-w|--web] [COMMAND|GUIDE] DESCRIPTIO

[PATCH v5 09/10] help: use command-list.txt for the source of guides

The help command currently hard codes the list of guides and their summary in C. Let's move this list to command-list.txt. This lets us extract summary lines from Documentation/git*.txt. This also potentially lets us list guides in git.txt, but I'll leave that for now. Signed-off-by: Nguyễn Thái

Re: [PATCH v4/wip 10/12] help: use command-list.txt for the source of guides

On Wed, Apr 25, 2018 at 12:31 PM, Nguyễn Thái Ngọc Duy <pclo...@gmail.com> wrote: > The help command currently hard codes the list of guides and their > summary in C. Let's move this list to command-list.txt. This lets us > extract summary lines from Documentation/git*.txt. This als

[PATCH v4/wip 09/12] help: add "-a --verbose" to list all commands with synopsis

ion/git-help.txt +++ b/Documentation/git-help.txt @@ -8,7 +8,7 @@ git-help - Display help information about Git SYNOPSIS [verse] -'git help' [-a|--all] [-g|--guide] +'git help' [-a|--all [--verbose]] [-g|--guide] [-i|--info|-m|--man|-w|--web] [COMMAND|GUIDE] DESCRIPTIO

[PATCH v4/wip 10/12] help: use command-list.txt for the source of guides

The help command currently hard codes the list of guides and their summary in C. Let's move this list to command-list.txt. This lets us extract summary lines from Documentation/git*.txt. This also potentially lets us lists guides in git.txt, but I'll leave that for now. Signed-off-by: Nguyễn Thái

[PATCH v4/wip 03/12] help: use command-list.h for common command list

The previous commit added code generation for all_cmd_desc[] which includes almost everything we need to generate common command list. Convert help code to use that array instead and drop common_cmds[] array. The description of each common command group is removed from command-list.txt

Re: [PATCH v3 6/6] help: use command-list.txt for the source of guides

On Sat, Apr 21, 2018 at 12:54 PM, Nguyễn Thái Ngọc Duy <pclo...@gmail.com> wrote: > The help command currently hard codes the list of guides and their > summary in C. Let's move this list to command-list.txt. This lets us > extract summary lines from Documentation/git*.txt. This als

[PATCH v3 5/6] help: add "-a --verbose" to list all commands with synopsis

40fc38d8b 100644 --- a/Documentation/git-help.txt +++ b/Documentation/git-help.txt @@ -8,7 +8,7 @@ git-help - Display help information about Git SYNOPSIS [verse] -'git help' [-a|--all] [-g|--guide] +'git help' [-a|--all [--verbose]] [-g|--guide] [-i|--info|-m|--man|-w|--web] [COMMAND|GUIDE

[PATCH v3 6/6] help: use command-list.txt for the source of guides

The help command currently hard codes the list of guides and their summary in C. Let's move this list to command-list.txt. This lets us extract summary lines from Documentation/git*.txt. This also potentially lets us lists guides in git.txt, but I'll leave that for now. Signed-off-by: Nguyễn Thái

[PATCH v2 6/6] help: use command-list.txt for the source of guides

The help command currently hard codes the list of guides and their summary in C. Let's move this list to command-list.txt. This lets us extract summary lines from Documentation/git*.txt. This also potentially lets us lists guides in git.txt, but I'll leave that for now. Signed-off-by: Nguyễn Thái

[PATCH v2 5/6] help: add "-a --verbose" to list all commands with synopsis

ocumentation/git-help.txt @@ -8,7 +8,7 @@ git-help - Display help information about Git SYNOPSIS [verse] -'git help' [-a|--all] [-g|--guide] +'git help' [-a|--all [--verbose]] [-g|--guide] [-i|--info|-m|--man|-w|--web] [COMMAND|GUIDE] DESCRIPTION @@ -42,6 +42,8 @

Re: Need help debugging issue in git

.e. what you get for "$0", > and 'b' and 'c' as the actual arguments to the "script". > > That is, you must fill in some dummy "script" name at slot [3], and > run_command chooses to put the alias text there. > >> I think the constant nesting of >&

Re: [PATCH/RFC 5/5] help: add "-a --verbose" to list all commands with synopsis

On Mon, Apr 9, 2018 at 11:55 AM, Eric Sunshine wrote: > On Mon, Apr 9, 2018 at 5:47 AM, Junio C Hamano wrote: >> Eric Sunshine writes: >>> On Mon, Mar 26, 2018 at 12:55 PM, Nguyễn Thái Ngọc Duy >>> wrote:

Re: [PATCH/RFC 5/5] help: add "-a --verbose" to list all commands with synopsis

On Mon, Apr 9, 2018 at 5:47 AM, Junio C Hamano wrote: > Eric Sunshine writes: >> On Mon, Mar 26, 2018 at 12:55 PM, Nguyễn Thái Ngọc Duy >> wrote: >>> + switch (category) { >>> + case CAT_ancillaryinterrogators: return

Re: [PATCH/RFC 5/5] help: add "-a --verbose" to list all commands with synopsis

Eric Sunshine writes: > On Mon, Mar 26, 2018 at 12:55 PM, Nguyễn Thái Ngọc Duy > wrote: >> Signed-off-by: Nguyễn Thái Ngọc Duy >> --- >> diff --git a/help.c b/help.c >> @@ -282,6 +282,67 @@ void list_porcelain_cmds(void) >> +static

Re: [PATCH/RFC 5/5] help: add "-a --verbose" to list all commands with synopsis

On Mon, Mar 26, 2018 at 12:55 PM, Nguyễn Thái Ngọc Duy wrote: > Signed-off-by: Nguyễn Thái Ngọc Duy > --- > diff --git a/help.c b/help.c > @@ -282,6 +282,67 @@ void list_porcelain_cmds(void) > +static const char *get_category_name(unsigned int category) > +{

Re: Need help debugging issue in git

Am 02.04.2018 um 02:36 schrieb Robert Dailey: I'm struggling with a bug that I found introduced in git v2.13.2. The bug was not reproducible in v2.13.1. The issue is that using arguments like "@{-1}" to aliases causes those curly braces to be removed, so once the command is executed after alias

Need help debugging issue in git

I'm struggling with a bug that I found introduced in git v2.13.2. The bug was not reproducible in v2.13.1. The issue is that using arguments like "@{-1}" to aliases causes those curly braces to be removed, so once the command is executed after alias processing the argument looks like "@-1". This

[PATCH/RFC 5/5] help: add "-a --verbose" to list all commands with synopsis

diff --git a/Documentation/git-help.txt b/Documentation/git-help.txt index 40d328a4b3..a40fc38d8b 100644 --- a/Documentation/git-help.txt +++ b/Documentation/git-help.txt @@ -8,7 +8,7 @@ git-help - Display help information about Git SYNOPSIS [verse] -'git help' [-a|--all] [-g|--guide]

Re: [GSoC] parse: not show usage help when invalid id

Roger Solano writes: > patch for too chatty command when is invalid > ex. git tag --contains > > It is possible to skip 'goto show_usage_error' when > parse_long_opt fails? and return directly from there. Can you explain how this relates to and/or compares with a recent

[GSoC] parse: not show usage help when invalid id

patch for too chatty command when is invalid ex. git tag --contains It is possible to skip 'goto show_usage_error' when parse_long_opt fails? and return directly from there. Signed-off-by: Roger Solano --- parse-options.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: Help...!

On Fri, Mar 16, 2018 at 07:38:07PM +0530, JYOTIK MAYUR wrote: > i am working on a project that is git hosting website like GitHub. I > am a student so i don't know much on how to make a website like GitHub > so could please tell me what can be the appropriate steps to make a > website like

Help...!

i am working on a project that is git hosting website like GitHub. I am a student so i don't know much on how to make a website like GitHub so could please tell me what can be the appropriate steps to make a website like that(mostly the server part).

Re: git help clone: questions

Am 07.03.2018 um 23:45 schrieb Junio C Hamano: > kalle writes: > >> Am 06.03.2018 um 02:36 schrieb Junio C Hamano: >>> kalle writes: >>> -In the explanation of the option --reference: shouldn't there be written '' instead of

Re: git help clone: questions

kalle writes: > Am 06.03.2018 um 02:36 schrieb Junio C Hamano: >> kalle writes: >> >>> -In the explanation of the option --reference: shouldn't there be >>> written '' instead of 'reference repository'? >> >> "Shouldn't X be Y?" is not an

Re: git help clone: questions

I wrote this, because when it is written about 'reference repository', I consider it not totally clear, which repository is meant, as the option '--reference ' only names one as . For reasons of clearness, I now propose writing "reference repository ". kalle Am 06.03.2018 um 02:36 schrieb Junio

Re: git help clone: questions

kalle writes: > -In the explanation of the option --reference: shouldn't there be > written '' instead of 'reference repository'? "Shouldn't X be Y?" is not an effective way to communicate; it solicits a "no, the current one is fine." without any explanation. If you

git help clone: questions

-In the explanation of the option --reference: shouldn't there be written '' instead of 'reference repository'? greetings, kalle

[PATCH v2 10/37] help: rename 'new' variables

Rename C++ keyword in order to bring the codebase closer to being able to be compiled with a C++ compiler. Signed-off-by: Brandon Williams --- builtin/help.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/builtin/help.c b/builtin/help.c index

[PATCH 0/3] add -p: improve help messages

From: Phillip Wood <phillip.w...@dunelm.org.uk> Improve the help displayed if the user presses an inactive key by only listing active keys and printing specific messages for some keys. Also disable search if there's only a single hunk. Phillip Wood (3): add -p: only display help for

[PATCH 1/3] add -p: only display help for active keys

From: Phillip Wood <phillip.w...@dunelm.org.uk> If the user presses a key that add -p wasn't expecting then it prints a list of key bindings. Although the prompt only lists the active bindings the help was printed for all bindings. Fix this by using the list of keys in the prompt to

I NEED YOUR HELP

in danger. I need your help in transferring my inheritance my father left behind for me in a Bank in Burkina Faso here, I have every information to guide you get the money transferred to your bank account, all i need is a foreigner who will stand as the foreign partner to my father and beneficiary

[PATCH] Documentation/git-send-email.txt: improve batching help

This clarifies that the relogin delay *must* be used in combination of `--batch-size` as there is no default for batch size, if the batch size is not given, we ignore the relogin delay argument. While at it, fix a typo in the batch size help. Signed-off-by: Stefan Beller <sbel...@google.

PLEASE I NEED YOUR HELP FOR MY EDUCATION

to leave my situation here to come over to your country to continue my education. I have made research before contacting you and please I want you to help me come to your country to start my new life. I will tell you more about my condition if you are willing to help me come over to your country

[PATCH 10/37] help: rename 'new' variables

Rename C++ keyword in order to bring the codebase closer to being able to be compiled with a C++ compiler. Signed-off-by: Brandon Williams --- builtin/help.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/builtin/help.c b/builtin/help.c index

Re: [PATCH 3/8] Doc/gitsubmodules: specify how submodules help in reduced size

e repositories tied together as >>>> + submodules in a superproject, you can avoid fetching the working >>>> + trees of the repositories you are not interested in. >>> >>> You do not fetch a working tree, but a whole repository? >>>

Re: [PATCH 3/8] Doc/gitsubmodules: specify how submodules help in reduced size

ng >>> + trees of the repositories you are not interested in. >> >> You do not fetch a working tree, but a whole repository? >> > > Maybe I misunderstood submodules when I wrote that example. Could you > help out with a better and precise replacement? If yo

Re: A cry for help, please don't ignore!

of transfering the fund. My father left a clause to the bank that i must introduce a trusted foreign partner who would be my trustee to help me invest this fund; hence the need for your assistance,i request that you be my ru stee and assist me in thi You will also be responsible for the investment

Re: [PATCH 3/8] Doc/gitsubmodules: specify how submodules help in reduced size

> + If you have your project as multiple repositories tied together as >> + submodules in a superproject, you can avoid fetching the working >> + trees of the repositories you are not interested in. > > You do not fetch a working tree, but a whole repository

Re: [PATCH 3/8] Doc/gitsubmodules: specify how submodules help in reduced size

On Sat, Jan 6, 2018 at 10:46 AM, Kaartic Sivaraam wrote: > Signed-off-by: Kaartic Sivaraam > --- > Documentation/gitsubmodules.txt | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/Documentation/gitsubmodules.txt

Re: [PATCH 3/8] Doc/gitsubmodules: specify how submodules help in reduced size

On Sat, Jan 6, 2018 at 1:46 PM, Kaartic Sivaraam wrote: > Signed-off-by: Kaartic Sivaraam > --- > diff --git a/Documentation/gitsubmodules.txt b/Documentation/gitsubmodules.txt > @@ -63,6 +63,9 @@ Submodules can be used for at least two

[PATCH 3/8] Doc/gitsubmodules: specify how submodules help in reduced size

Signed-off-by: Kaartic Sivaraam --- Documentation/gitsubmodules.txt | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Documentation/gitsubmodules.txt b/Documentation/gitsubmodules.txt index cb795c6b6..3f73983d5 100644 --- a/Documentation/gitsubmodules.txt +++

<    1   2   3   4   5   6   7   8   9   10   >