From: Denton Liu <liu.denton@gmail.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org
Subject: Why isn't 'jch' based on 'next'?
Date: Thu, 15 Apr 2021 02:12:02 -0700 [thread overview]
Message-ID: <YHgDYl3cMx9+Hqa7@generichostname> (raw)
Hi Junio,
Out of curiosity, why is 'jch' not based on 'next' but instead, it
recreates the same merge commits on top of 'master'. What is the
advantage of this?
Thanks,
Denton
next reply other threads:[~2021-04-15 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 9:12 Denton Liu [this message]
2021-04-15 18:24 ` Why isn't 'jch' based on 'next'? Junio C Hamano
2021-04-15 19:46 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YHgDYl3cMx9+Hqa7@generichostname \
--to=liu.denton@gmail.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.
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 NNTP newsgroup(s).