From: 胡哲宁 <adlternative@gmail.com>
To: gitster@pobox.com
Cc: adlternative@gmail.com, git@vger.kernel.org, gitgitgadget@gmail.com
Subject: Re: Re* [PATCH] builtin/*: update usage format
Date: Wed, 6 Jan 2021 19:07:09 +0800 [thread overview]
Message-ID: <CAOLTT8ToMq9_E+-bUiTG7PnM=rQZZ2rTPS=4Y5rO9QsUJUZhOg@mail.gmail.com> (raw)
In fact, this patch is to complete the problem described in this issue:
https://github.com/gitgitgadget/git/issues/636
I don't notice I should write it to commit message before ,My wrong !
Thank you for the patch, Junio.
Your help is great for our novices. :-)
next reply other threads:[~2021-01-06 11:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 11:07 胡哲宁 [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-29 8:55 [PATCH] builtin/*: update usage format 阿德烈 via GitGitGadget
2021-01-06 7:05 ` Re* " Junio C Hamano
2021-01-06 12:03 ` Derrick Stolee
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='CAOLTT8ToMq9_E+-bUiTG7PnM=rQZZ2rTPS=4Y5rO9QsUJUZhOg@mail.gmail.com' \
--to=adlternative@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=gitster@pobox.com \
/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.