git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: "Bagas Sanjaya" <bagasdotme@gmail.com>,
	"Git List" <git@vger.kernel.org>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Glen Choo" <chooglen@google.com>
Subject: Re: [PATCH] MyFirstContribution: teach to use "format-patch --base=auto"
Date: Sat, 23 Oct 2021 14:03:35 -0700	[thread overview]
Message-ID: <xmqqh7d7bgig.fsf@gitster.g> (raw)
In-Reply-To: <CAPig+cSgEvxVBUhrVf9ceG5L1DU5qTbfOgo=wOsOja1X8y+pfg@mail.gmail.com> (Eric Sunshine's message of "Fri, 22 Oct 2021 02:48:02 -0400")

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Fri, Oct 22, 2021 at 2:43 AM Bagas Sanjaya <bagasdotme@gmail.com> wrote:
>> From: Junio C Hamano <gitster@pobox.com>
>>
>> Let's encourage first-time contributors to tell us what commit they
>> based their work with the format-patch invocation. As the example
>> already forks from origin/master and branch.autosetupmerge by
>> default records the upstream when the psuh branch was created, we
>> can use --base=auto for this.  Also, mention to the readers that the
>> range of commits can simply be given with `@{u}` if they are on the
>> `psuh` branch already.
>>
>> As we are getting one more option on the command line, and spending
>> one paragraph each to explain them, let's reformat that part of the
>> description as a bulletted list.
>
> s/bulletted/bulleted/

Thanks; will fix locally.

  reply	other threads:[~2021-10-23 21:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  6:40 [PATCH] MyFirstContribution: teach to use "format-patch --base=auto" Bagas Sanjaya
2021-10-22  6:48 ` Eric Sunshine
2021-10-23 21:03   ` Junio C Hamano [this message]
2021-10-23 21:01 ` Junio C Hamano

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=xmqqh7d7bgig.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=avarab@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=chooglen@google.com \
    --cc=git@vger.kernel.org \
    --cc=sunshine@sunshineco.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).