greened@xxxxxxxxxxxxx (David A. Greene) writes:
>> But more important than the physical layout is the maintenance plan
>> going forward. Is Avery going to keep maintaining git-subtree, and we
>> will just occasionally pull? Are you maintaining it? Where will patches
>> go? To a github repo? To git@vger?
>
> I am still waiting to hear from Avery on that. I will ping him again.
> My intention is to certainly participate in maintenance. I use
> git-subtree daily so it's in my interest to keep it working.
I've attached Avery's response below. The short summary is that he
thinks maintaining it in the vger git repository is the way to go and
that he's fine moving patches to/from GitHub as necessary.
So again, I will certainly be part of the maintenance team. There are a
few other people currently helping out with maintenance and I will help
Avery to get the word out about the switch as he requires.
-Dave
--8<-----------------------------------------------------------------------
Thanks for putting work into this. You can feel free to cc: me on any
git-list discussions if you want.
I haven't done any significant amount of git-subtree maintenance lately,
but even if I did, since it's only one file it should be easy to put
move patches between github and git whenever we want. I would suggest
that just maintaining it as part of git is the best way to go, since
having diverging versions doesn't really help anyone.
I'm sure the potential benefit of putting git-subtree in the contrib/
directory is that we could then use git-subtree to maintain the
git-subtree git subtree, which is a fun wordplay, but perhaps
ironically, as a single rarely-changing file, git-subtree is probably
not the right tool for these purposes :)
Have fun,
Avery
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html