From: Fabian Stelzer <fs@gigacodes.de>
To: tqfx su <sutqfx@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-subtree
Date: Mon, 15 Nov 2021 09:12:07 +0100 [thread overview]
Message-ID: <20211115081207.vpef4i3rdfr7gljy@fs> (raw)
In-Reply-To: <CAH6-BcyoEy29-NPCqivWTPoqM0e8=Pp1ahrCaZpBko8cSyv-6Q@mail.gmail.com>
On 14.11.2021 18:11, tqfx su wrote:
>git maintainers,
> Can you add a GPG signature option to git-subtree?
> I do hope you can take the above suggestions into consideration and
>thanks in advance.
Hi,
i suspect you'd like the squash & merge commits the subtree commands
create to be signed? If so you can try simply enabling commit.gpgsign in
your config before doing a subtree operation. This will cause all
commits to be signed. If this works as you expect we could make subtree
pass a "-s" flag for signing on to the commit calls.
next prev parent reply other threads:[~2021-11-15 8:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-14 10:11 git-subtree tqfx su
2021-11-15 8:12 ` Fabian Stelzer [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-04 15:53 git-subtree David Greene
2012-01-05 11:28 ` git-subtree Ramkumar Ramachandra
2012-01-05 15:03 ` git-subtree David A. Greene
2012-01-05 15:32 ` git-subtree Ramkumar Ramachandra
2012-01-05 16:33 ` git-subtree David A. Greene
2012-01-06 1:53 ` git-subtree David A. Greene
2012-01-05 22:18 ` git-subtree David A. Greene
2012-01-05 15:47 ` git-subtree Jeff King
2012-01-05 16:26 ` git-subtree David A. Greene
2012-01-29 22:07 ` git-subtree David A. Greene
2012-01-30 16:56 ` git-subtree David A. Greene
2012-01-05 22:16 ` git-subtree David A. Greene
2012-01-05 15:53 ` git-subtree Junio C Hamano
2012-01-05 16:48 ` git-subtree David A. Greene
2012-01-05 22:19 ` git-subtree David A. Greene
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=20211115081207.vpef4i3rdfr7gljy@fs \
--to=fs@gigacodes.de \
--cc=git@vger.kernel.org \
--cc=sutqfx@gmail.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).