From: Derrick Stolee <stolee@gmail.com>
To: Cameron Steffen via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/1] doc: small formatting fix
Date: Wed, 11 Sep 2019 07:49:07 -0400 [thread overview]
Message-ID: <2f301b94-f8da-3a36-8d3b-08593ceb1a5a@gmail.com> (raw)
In-Reply-To: <pull.330.git.gitgitgadget@gmail.com>
On 9/9/2019 7:21 PM, Cameron Steffen via GitGitGadget wrote:
> Edit: I need permission to submit please
Hi Cameron.
When using GitGitGadget, your PR description becomes your cover letter on the mailing list. This is a great place for you to describe how you discovered this problem and if you have looked elsewhere for similar issues to fix up.
Thanks,
-Stolee
>
> Cameron Steffen (1):
> doc: small formatting fix
>
> Documentation/pretty-formats.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
> base-commit: 75b2f01a0f642b39b0f29b6218515df9b5eb798e
> Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-330%2Fcamsteffen%2Fpatch-1-v1
> Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-330/camsteffen/patch-1-v1
> Pull-Request: https://github.com/gitgitgadget/git/pull/330
>
next prev parent reply other threads:[~2019-09-11 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 23:21 [PATCH 0/1] doc: small formatting fix Cameron Steffen via GitGitGadget
2019-09-09 23:21 ` [PATCH 1/1] " Cameron Steffen via GitGitGadget
2019-09-11 11:50 ` Derrick Stolee
2019-09-11 21:24 ` Johannes Schindelin
2019-09-11 11:49 ` Derrick Stolee [this message]
2019-09-11 14:52 ` [PATCH v2 0/1] " Cameron Steffen via GitGitGadget
2019-09-11 14:52 ` [PATCH v2 1/1] doc: minor " Cameron Steffen via GitGitGadget
2019-09-12 18:06 ` Junio C Hamano
2019-09-11 21:21 ` [PATCH 0/1] doc: small " Johannes Schindelin
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2f301b94-f8da-3a36-8d3b-08593ceb1a5a@gmail.com \
--to=stolee@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).