From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Glen Choo <chooglen@google.com>, git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Carlo Arenas <carenas@gmail.com>
Subject: Re: [PATCH v2] Documentation: specify base point when generating MyFirstContribution patchset
Date: Sat, 16 Oct 2021 12:16:29 +0700 [thread overview]
Message-ID: <35ccb414-c0fe-ab3a-21aa-ac7b1338df6a@gmail.com> (raw)
In-Reply-To: <kl6l4k9i1ame.fsf@chooglen-macbookpro.roam.corp.google.com>
On 16/10/21 00.06, Glen Choo wrote:
> This reads quite awkwardly because a few lines above, we already tell
> the reader exactly what commands to run:
>
> Sending emails with Git is a two-part process; before you can prepare the emails
> themselves, you'll need to prepare the patches. Luckily, this is pretty simple:
>
> ----
> $ git format-patch --cover-letter -o psuh/ master..psuh
> ----
>
> If we do accept this suggestion (and I am not sure if we should, because
> as Junio said, there are strong conventions for determining the branch
> point), I think this would be easier to follow if we incorporate it into
> the existing instructions. Something like..
>
> Sending emails with Git is a two-part process; before you can prepare the emails
> themselves, you'll need to prepare the patches. Luckily, this is
> pretty simple. First, we'll get the hash of the commit the patchset is
> based on. We call this commit the 'base'.
>
> ----
> $ git show -s --format="%H" master
> ----
>
> Now, we'll generate the patches, passing the hash of the 'base' to the
> --base option.
>
> ----
> $ git format-patch --cover-letter --base=<base> -o psuh/ master..psuh
> ----
>
> [...describe --base=<base> the way we describe the other options].
>
Actually it is up to contributors whether they want to include `--base`
or not.
--
An old man doll... just what I always wanted! - Clara
next prev parent reply other threads:[~2021-10-16 5:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 12:25 [PATCH v2] Documentation: specify base point when generating MyFirstContribution patchset Bagas Sanjaya
2021-10-15 17:06 ` Glen Choo
2021-10-16 5:16 ` Bagas Sanjaya [this message]
2021-10-15 17:14 ` 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=35ccb414-c0fe-ab3a-21aa-ac7b1338df6a@gmail.com \
--to=bagasdotme@gmail.com \
--cc=carenas@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).