From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Stephen R Guglielmo <srguglielmo@gmail.com>,
Avery Pennarun <apenwarr@gmail.com>, git <git@vger.kernel.org>
Subject: Re: Bug Report: Subtrees and GPG Signed Commits
Date: Tue, 30 Jan 2018 15:24:30 -0800 [thread overview]
Message-ID: <xmqqy3kfq6a9.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAGZ79kafgyOujDM4BsXdDUnP+iFk5mp2bYnX-Q65khW-weEhUg@mail.gmail.com> (Stefan Beller's message of "Tue, 30 Jan 2018 15:17:31 -0800")
Stefan Beller <sbeller@google.com> writes:
> There has not been feedback for a while on this thread.
> I think that is because subtrees are not in anyone's hot
> interest area currently.
>
> This is definitely the right place to submit&discuss bugs.
> Looking through "git log --format="%ae %s" -S subtree",
> it seems as if Avery (apenwarr@gmail.com) was mostly
> interested in developing subtrees, though I think he has
> moved on. Originally it was invented by Junio, who is
> the active maintainer of the project in 68faf68938
> (A new merge stragety 'subtree'., 2007-02-15)
Thanks for trying to help, but I have *NOTHING* to do with the "git
subtree" subcommand (and I personally have no interest in it). What
I did was a subtree merge strategy (i.e. "git merge -s subtree"),
which is totally a different thing.
David Greene offered to take it over in 2015, and then we saw some
activity by David Aguilar in 2016, but otherwise the subcommand from
contrib/ has pretty much been dormant these days.
next prev parent reply other threads:[~2018-01-30 23:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-06 22:45 Bug Report: Subtrees and GPG Signed Commits Stephen R Guglielmo
2018-01-18 16:19 ` Stephen R Guglielmo
2018-01-30 19:15 ` Stephen R Guglielmo
2018-01-30 23:17 ` Stefan Beller
2018-01-30 23:24 ` Junio C Hamano [this message]
2018-01-30 23:37 ` Avery Pennarun
2018-01-31 12:33 ` Stephen R Guglielmo
2018-02-02 23:39 ` Junio C Hamano
2018-02-05 14:30 ` Stephen R Guglielmo
2018-02-05 14:40 ` Stephen R Guglielmo
2018-02-05 18:45 ` Junio C Hamano
2018-02-08 13:53 ` Stephen R Guglielmo
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=xmqqy3kfq6a9.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
--cc=srguglielmo@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.
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).