{"thread":{"id":"60409","subject":"[PATCH] git-push: more visibility for -q option","startedAt":"2023-10-20T18:46:40Z","lastAt":"2023-10-30T10:40:47Z","messageCount":4,"participants":["Michal Suchanek","Eric Sunshine","Junio C Hamano","Michal Suchánek"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"483590","messageId":"20231020184627.14336-1-msuchanek@suse.de","threadId":"60409","inReplyTo":null,"subject":"[PATCH] git-push: more visibility for -q option","fromName":"Michal Suchanek","fromEmail":"msuchanek@suse.de","sentAt":"2023-10-20T18:45:21Z","receivedAt":"2023-10-20T18:46:40Z","isPatch":true,"sender":{"key":"msuchanek@suse.de","avatar":"https://avatars.githubusercontent.com/u/787652?v=4"},"body":"The -v option listed at the top as option al parameter while -q is not.\n\nList -q alongside -v.\n\nSigned-off-by: Michal Suchanek <msuchanek@suse.de>\n---\n Documentation/git-push.txt | 2 +-\n 1 file changed, 1 insertion(+), 1 deletion(-)\n\ndiff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\nindex 5b4edaf4a8..003bc7d9ce 100644\n--- a/Documentation/git-push.txt\n+++ b/Documentation/git-push.txt\n@@ -10,7 +10,7 @@ SYNOPSIS\n --------\n [verse]\n 'git push' [--all | --branches | --mirror | --tags] [--follow-tags] [--atomic] [-n | --dry-run] [--receive-pack=<git-receive-pack>]\n-\t   [--repo=<repository>] [-f | --force] [-d | --delete] [--prune] [-v | --verbose]\n+\t   [--repo=<repository>] [-f | --force] [-d | --delete] [--prune] [-q | --quiet] [-v | --verbose]\n \t   [-u | --set-upstream] [-o <string> | --push-option=<string>]\n \t   [--[no-]signed|--signed=(true|false|if-asked)]\n \t   [--force-with-lease[=<refname>[:<expect>]] [--force-if-includes]]\n-- \n2.42.0\n\n"},{"id":"483598","messageId":"CAPig+cTGiFSkC4dXwmXhaM9wxnr4SDnpzV4Y7yY8ti708zuiZg@mail.gmail.com","threadId":"60409","inReplyTo":"20231020184627.14336-1-msuchanek@suse.de","subject":"Re: [PATCH] git-push: more visibility for -q option","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2023-10-20T20:05:27Z","receivedAt":"2023-10-20T20:05:40Z","isPatch":true,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Fri, Oct 20, 2023 at 2:46 PM Michal Suchanek <msuchanek@suse.de> wrote:\n> The -v option listed at the top as option al parameter while -q is not.\n\ns/option al/optional/\n\n> List -q alongside -v.\n>\n> Signed-off-by: Michal Suchanek <msuchanek@suse.de>\n"},{"id":"483599","messageId":"xmqqwmvhoy57.fsf@gitster.g","threadId":"60409","inReplyTo":"20231020184627.14336-1-msuchanek@suse.de","subject":"Re: [PATCH] git-push: more visibility for -q option","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2023-10-20T20:08:04Z","receivedAt":"2023-10-20T20:08:10Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Michal Suchanek <msuchanek@suse.de> writes:\n\n> The -v option listed at the top as option al parameter while -q is not.\n\n\"as option al parameter\" - ECANNOTPARSE.  Probably\n\n    The `-v` option is shown in the SYNOPSIS section near the top,\n    but `-q` is not shown anywhere there.\n\nor something, I think.  I agree showing it next to \"-v\" would make\nthe most sense.\n\n>\n> List -q alongside -v.\n>\n> Signed-off-by: Michal Suchanek <msuchanek@suse.de>\n> ---\n>  Documentation/git-push.txt | 2 +-\n>  1 file changed, 1 insertion(+), 1 deletion(-)\n>\n> diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\n> index 5b4edaf4a8..003bc7d9ce 100644\n> --- a/Documentation/git-push.txt\n> +++ b/Documentation/git-push.txt\n> @@ -10,7 +10,7 @@ SYNOPSIS\n>  --------\n>  [verse]\n>  'git push' [--all | --branches | --mirror | --tags] [--follow-tags] [--atomic] [-n | --dry-run] [--receive-pack=<git-receive-pack>]\n> -\t   [--repo=<repository>] [-f | --force] [-d | --delete] [--prune] [-v | --verbose]\n> +\t   [--repo=<repository>] [-f | --force] [-d | --delete] [--prune] [-q | --quiet] [-v | --verbose]\n\nYup, the change makes sense.  We may want to wrap the first line to\na more reasonable length in a separate commit, and when that\nhappens, we probably would want to start [-v] [-q] on a separate\nline as well, but for now this would do.\n\n"},{"id":"484094","messageId":"20231030104041.GJ6241@kitsune.suse.cz","threadId":"60409","inReplyTo":"xmqqwmvhoy57.fsf@gitster.g","subject":"Re: [PATCH] git-push: more visibility for -q option","fromName":"Michal Suchánek","fromEmail":"msuchanek@suse.de","sentAt":"2023-10-30T10:40:41Z","receivedAt":"2023-10-30T10:40:47Z","isPatch":true,"sender":{"key":"msuchanek@suse.de","avatar":"https://avatars.githubusercontent.com/u/787652?v=4"},"body":"Hello,\n\nOn Fri, Oct 20, 2023 at 01:08:04PM -0700, Junio C Hamano wrote:\n> Michal Suchanek <msuchanek@suse.de> writes:\n> \n> > The -v option listed at the top as option al parameter while -q is not.\n> \n> \"as option al parameter\" - ECANNOTPARSE.  Probably\n> \n>     The `-v` option is shown in the SYNOPSIS section near the top,\n>     but `-q` is not shown anywhere there.\n> \n> or something, I think.  I agree showing it next to \"-v\" would make\n> the most sense.\n\nwhen rebasing to current master I see this is already applied with the\nfixed commit message, great!\n\nThanks\n\nMichal\n\n> \n> >\n> > List -q alongside -v.\n> >\n> > Signed-off-by: Michal Suchanek <msuchanek@suse.de>\n> > ---\n> >  Documentation/git-push.txt | 2 +-\n> >  1 file changed, 1 insertion(+), 1 deletion(-)\n> >\n> > diff --git a/Documentation/git-push.txt b/Documentation/git-push.txt\n> > index 5b4edaf4a8..003bc7d9ce 100644\n> > --- a/Documentation/git-push.txt\n> > +++ b/Documentation/git-push.txt\n> > @@ -10,7 +10,7 @@ SYNOPSIS\n> >  --------\n> >  [verse]\n> >  'git push' [--all | --branches | --mirror | --tags] [--follow-tags] [--atomic] [-n | --dry-run] [--receive-pack=<git-receive-pack>]\n> > -\t   [--repo=<repository>] [-f | --force] [-d | --delete] [--prune] [-v | --verbose]\n> > +\t   [--repo=<repository>] [-f | --force] [-d | --delete] [--prune] [-q | --quiet] [-v | --verbose]\n> \n> Yup, the change makes sense.  We may want to wrap the first line to\n> a more reasonable length in a separate commit, and when that\n> happens, we probably would want to start [-v] [-q] on a separate\n> line as well, but for now this would do.\n> \n"}]}