From: Junio C Hamano <gitster@pobox.com>
To: Stephen R Guglielmo <srguglielmo@gmail.com>
Cc: Avery Pennarun <apenwarr@gmail.com>,
Stefan Beller <sbeller@google.com>, git <git@vger.kernel.org>
Subject: Re: Bug Report: Subtrees and GPG Signed Commits
Date: Fri, 02 Feb 2018 15:39:00 -0800 [thread overview]
Message-ID: <xmqqpo5narmz.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CADfK3RXOqB7wKnXCWxgyDeov-Y7rVQiWFUa_hKZk=j9ReY9JDQ@mail.gmail.com> (Stephen R. Guglielmo's message of "Wed, 31 Jan 2018 07:33:57 -0500")
Stephen R Guglielmo <srguglielmo@gmail.com> writes:
> 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.
next prev parent reply other threads:[~2018-02-02 23:39 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
2018-01-30 23:37 ` Avery Pennarun
2018-01-31 12:33 ` Stephen R Guglielmo
2018-02-02 23:39 ` Junio C Hamano [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqpo5narmz.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.
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).