git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Glen Choo <chooglen@google.com>,
	Bagas Sanjaya <bagasdotme@gmail.com>,
	Git List <git@vger.kernel.org>
Subject: Re: Re* [PATCH v3] Documentation: specify base point when generating MyFirstContribution patchset
Date: Tue, 19 Oct 2021 00:36:50 -0400	[thread overview]
Message-ID: <CAPig+cQU_TF-MbOv-PaE-0L5dEa_rgDXptOLAu+JOAn=RuJCqg@mail.gmail.com> (raw)
In-Reply-To: <xmqqwnmaumcz.fsf_-_@gitster.g>

On Mon, Oct 18, 2021 at 4:09 PM Junio C Hamano <gitster@pobox.com> wrote:
> Subject: [PATCH] MyFirstContribution: teach to use "format-patch --base=auto"
>
> 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 by branch.autosetupmerge by

I think you meant: s/and by/and/

> default records the upstream when the psuh branch was created, we
> can use --base=auto for this.  Also, mention the readers that the

s/the readers/to readers/

> 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.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>

      reply	other threads:[~2021-10-19  4:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 12:41 [PATCH v3] Documentation: specify base point when generating MyFirstContribution patchset Bagas Sanjaya
2021-10-18 17:09 ` Junio C Hamano
2021-10-18 17:32   ` Glen Choo
2021-10-18 20:08     ` Re* " Junio C Hamano
2021-10-19  4:36       ` Eric Sunshine [this message]

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='CAPig+cQU_TF-MbOv-PaE-0L5dEa_rgDXptOLAu+JOAn=RuJCqg@mail.gmail.com' \
    --to=sunshine@sunshineco.com \
    --cc=bagasdotme@gmail.com \
    --cc=chooglen@google.com \
    --cc=git@vger.kernel.org \
    --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).