All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gummerer <t.gummerer@gmail.com>
To: Alangi Derick <alangiderick@gmail.com>, git@vger.kernel.org
Subject: Re: [Patch] Nice help Output - SmallProjectIdea[1]
Date: Fri, 01 May 2015 21:11:12 +0200	[thread overview]
Message-ID: <87wq0sw1tb.fsf@hank.tgummerer.com> (raw)
In-Reply-To: <CAKB+oNvZxueR9PqysPn3khQZL+8tt3NNrgFzNjHnVuBVtyeZ4w@mail.gmail.com>

Hi,

Alangi Derick <alangiderick@gmail.com> writes:

> This is a patch to fix the problem as given in the site:
> https://git.wiki.kernel.org/index.php/SmallProjectsIdeas

Please have a look at Documentation/SubmittingPatches, on how to submit
well formed patches.  In particular, the following things should be
improved:

- The commit should have a meaningful commit message (See section 2 in
  SubmittingPatches)
- The patch should be created with git format-patch, so it can be
  applied using git am. (See section 3 and 4)
- Your work should be signed off, otherwise it can not be applied to the
  project. (See section 5)

> diff --git a/help.c b/help.c
> index 2072a87..e347bbc 100644
> --- a/help.c
> +++ b/help.c
> @@ -229,9 +229,18 @@ void list_common_cmds_help(void)
>
>   puts(_("The most commonly used git commands are:"));
>   for (i = 0; i < ARRAY_SIZE(common_cmds); i++) {
> - printf("   %s   ", common_cmds[i].name);
> - mput_char(' ', longest - strlen(common_cmds[i].name));
> - puts(_(common_cmds[i].help));
> + if(i%3 == 1){
> + printf("   %s   ", common_cmds[i].name);
> + mput_char(' ', longest - strlen(common_cmds[i].name));
> + puts(_(common_cmds[i].help));
> + printf("\n");
> + }
> + else {
> + printf("   %s   ", common_cmds[i].name);
> + mput_char(' ', longest - strlen(common_cmds[i].name));
> + puts(_(common_cmds[i].help));
> + }
> +

Patch formatting issues aside, I don't think this does what is suggested
in the project.  You are just adding a blank line after three lines in
the help output, which I don't think improves the current state by much.

The bzr help output on the other hand groups similar commands together,
and shows them to the user in groups.  So the first step would be to
find out which commands should be grouped together and then to output
the groups here.

>   }
>  }
>
>
> Regards
> Alangi Derick Ndimnain
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2015-05-01 19:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 18:33 [Patch] Nice help Output - SmallProjectIdea[1] Alangi Derick
2015-05-01 19:11 ` Thomas Gummerer [this message]
2015-05-02  7:04   ` Alangi Derick
2015-05-02  9:51     ` Thomas Gummerer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wq0sw1tb.fsf@hank.tgummerer.com \
    --to=t.gummerer@gmail.com \
    --cc=alangiderick@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.