From: Junio C Hamano <gitster@pobox•com>
To: Adam Spiers <git@adamspiers•org>
Cc: Jeremy Rosen <jeremy.rosen@openwide•fr>,
David Greene <greened@obbligato•org>,
git@vger•kernel.org
Subject: Re: Subtree: My Status
Date: Mon, 16 Dec 2013 11:18:14 -0800 [thread overview]
Message-ID: <xmqq4n68ppu1.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20131214153351.GB31739@pacific.linksys.moosehall> (Adam Spiers's message of "Sat, 14 Dec 2013 15:33:51 +0000")
Adam Spiers <git@adamspiers•org> writes:
>> Somebody take the ownership of the area, if David Green who earlier
>> volunteered to do so and worked on it needs help reviewing, helping
>> polishing and giving thumbs-up on the patches, perhaps?
>
> I *may* be able to help a bit in the coming weeks, given that it's
> reasonably likely I'll be using git-subtree for professional reasons.
>
> However I'm not clear from the above whether you're suggesting that
> someone should take over ownership from David, or merely help him?
I'll leave that between you and David, and possibly other people who
are interested in advancing "git subtree" who may volunteer.
> And in either case, what would be your criteria and process for
> accepting patches, given that ultimately you're still in control of
> the repository?
I'd imagine for the first few rounds of patchsets I'll be picky
about styles and design, but once whoever eventually becomes the
volunteer subarea maintainer (perhaps you) demonsrates that s/he has
good enough motivation and taste to keep the codebase clean and user
experience consistent, I'd delegate more and more decision what to
include and reject to that subarea maintainer, just like any
material in the contrib/ area.
prev parent reply other threads:[~2013-12-16 19:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 17:59 Subtree: My Status greened
2013-04-22 7:18 ` Jeremy Rosen
2013-12-12 18:24 ` Adam Spiers
2013-12-12 19:26 ` Junio C Hamano
2013-12-14 15:33 ` Adam Spiers
2013-12-16 19:18 ` Junio C Hamano [this message]
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=xmqq4n68ppu1.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@adamspiers$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=greened@obbligato$(echo .)org \
--cc=jeremy.rosen@openwide$(echo .)fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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