From: Matthew Ogilvie <mmogilvi_git@miniinfo.net>
To: James Denholm <nod.helm@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] subtree/Makefile: Standardize (esp. for packagers)
Date: Tue, 29 Apr 2014 21:20:45 -0600 [thread overview]
Message-ID: <20140430032045.GA4613@comcast.net> (raw)
In-Reply-To: <6a7bcc79-d9c3-4cf8-8f3b-a6a16298c221@email.android.com>
On Sun, Apr 27, 2014 at 12:35:13PM +1000, James Denholm wrote:
> Jeff King <peff@peff.net> wrote:
> >I think the problem is that
> >contrib/subtree does not really have an active dedicated area
> >maintainer.
>
> Yeah, I can see how that might become a bit of a problem. I was
> actually thinking of doing a bit of work on subtree beyond this
> specific patch, so hopefully that won't be a show-stopper. We'll
> see what happens, I guess.
Agreed. It also doesn't help that when subtree patches are proposed
(especially new features instead of obvious bugs), there often seems
to be little or no feedback from anyone.
--------
Depending on how much time you have:
This may be outside the scope of work you were planning on, but
it might be worth grepping through old mailing list archives for
"subtree" patches that haven't been merged, and see if there is
anything worth revisiting/resubmitting. I believe most of the
following (at least) kind of languished and died, often with little
or no real review and feedback:
http://marc.info/?l=git&m=138644067726844&w=2
http://marc.info/?l=git&m=138523794407181&w=2
- My own series, plus another patch that has roughly the
same description, but different semantics.
http://marc.info/?l=git&m=136321400525507&w=2
http://marc.info/?l=git&m=136321400525507&w=2
- Some series from Paul Campbell.
http://marc.info/?l=git&m=136122107605036&w=2
http://marc.info/?l=git&m=135813589922554&w=2
http://marc.info/?l=git&m=136415434127550&w=2
http://marc.info/?l=git&m=136127692217856&w=2
- Other series.
http://marc.info/?l=git&m=138557714926045&w=2
http://marc.info/?l=git&m=138129106613560&w=2
http://marc.info/?l=git&m=136415882128742&w=2
http://marc.info/?l=git&m=136415654228062&w=2
- Miscellaneous
And probably others...
(I don't know if these are the latest or "best" versions of these, nor
have I really looked at them closely to decide if they are worth
including at all. Be sure to exameine not just the discussion around
the specific patches, but also the other patches in each series...)
- Matthew Ogilvie
next prev parent reply other threads:[~2014-04-30 3:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 1:52 [PATCH] subtree/Makefile: Standardize (esp. for packagers) nod.helm
[not found] ` <CAHYYfeGNDLVxzP6zMyJnSi8GxpQaUKGAkqaLfXbZ=8B1k7vvyQ@mail.gmail.com>
2014-04-26 4:56 ` nod.helm
2014-04-26 7:25 ` Jeff King
2014-04-27 2:35 ` James Denholm
2014-04-27 2:51 ` Jeff King
2014-04-27 3:01 ` James Denholm
2014-04-30 3:20 ` Matthew Ogilvie [this message]
2014-05-03 12:56 ` James Denholm
2014-05-03 19:22 ` Felipe Contreras
2014-05-03 22:12 ` James Denholm
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=20140430032045.GA4613@comcast.net \
--to=mmogilvi_git@miniinfo.net \
--cc=git@vger.kernel.org \
--cc=nod.helm@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).