Re: Bug Report: Subtrees and GPG Signed Commits

From: Junio C Hamano <gitster@pobox.com>
Date: Feb 2, 2018, 23:39 UTC
Message-ID: <xmqqpo5narmz.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <CADfK3RXOqB7wKnXCWxgyDeov-Y7rVQiWFUa_hKZk=j9ReY9JDQ@mail.gmail.com>

Stephen R Guglielmo <srguglielmo@gmail.com> writes:

Show 20 quoted lines

> On Tue, Jan 30, 2018 at 6:37 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
>>
>> Sorry I can't help more.
>>
>> Good luck,
>>
>> Avery
>
> Thanks all for the discussion/replies.
>
> We use subtrees extensively in our environment right now. The "sub"
> repos (90+) are located on GitHub, while the "main/parent" repo is
> provided by a vendor on website hosting infrastructure.
>
> I will take a look at:
> git/Documentation/CodingGuidelines
> git/Documentation/SubmittingPatches
> git/contrib/subtree/
>
> Should I follow up in this thread with a patch (it might be a while)?

These three are good place to start at. You may find the output of "git shortlog --no-merges --since=N.months contrib/subtree" and "git blame contrib/subtree" also a good source of whom to ask for help. As we said on this thread, this is a corner of the contrib/ section that nobody seems to be actively working on, so if you really depend on it working well, you might have to take the ownership of it ;-)

Thanks.