Re: [RFC] Moving main git-subtree development. to GitHub

From: Jonathan Nieder <jrnieder@gmail.com>
Date: Aug 1, 2017, 17:52 UTC
Message-ID: <20170801175236.GS13924@aiede.mtv.corp.google.com>
In-Reply-To: <87mv7kf369.fsf@waller.obbligato.org>

Hi,

David A. Greene wrote:

>                                                             Essentially,
> I would like to do a "beta" release of the new code while not impacting
> existing users of git-subtree in contrib.

Sounds like a sensible goal. In-tree, you can do that by saying "please merge this branch to 'next', but I do not want it in 'master' yet". But doing it out-of-tree is even more straightforward, since you have complete control of the repository people use and do not have to wait for git to pull in your latest changes.

[...]

> I believe keeping a stable git-subtree in contrib is valuable.

I am not convinced of this. git-subtree is a well known tool, and in its role as a separate project then I think distributors are actually more likely to package it for easy installation by users. The usual benefit of contrib of providing visibility for a new project seems to have already occurred and not be needed as much as it used to be for this project --- by now it is a very visible project.

[...]

> Does this mode of operation work for the larger git community?  Are
> there suggestions of how to make this work as smoothly as possible?

That said, if we want to keep it in contrib then I think the mode of operation you described is a good one.

Thanks for your work, Jonathan