From: Felipe Contreras <felipe.contreras@gmail.com>
To: James Denholm <nod.helm@gmail.com>,
Matthew Ogilvie <mmogilvi_git@miniinfo.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] subtree/Makefile: Standardize (esp. for packagers)
Date: Sat, 03 May 2014 14:22:48 -0500 [thread overview]
Message-ID: <5365420874947_27397d32f016@nysa.notmuch> (raw)
In-Reply-To: <CAHYYfeGNO5QknoKkZfYy3XLNRZsVmf0WjeNGkDxH3QwPF-RsUQ@mail.gmail.com>
James Denholm wrote:
> Matthew Ogilvie <mmogilvi_git@miniinfo.net> wrote:
> > On Sun, Apr 27, 2014 at 12:35:13PM +1000, James Denholm wrote:
> >> Jeff King <peff@peff.net> wrote:
> > 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,
>
> While current, immediate focus is really just getting the makefile fixed
> up and hopefully then have more people package subtree by default,
> overall I'll very likely extend that to general work on subtree and such.
I think you should take a look at the Makefile of
contrib/remote-helpers. I bet something simple like that would work just
fine for subtree.
--
Felipe Contreras
next prev parent reply other threads:[~2014-05-03 19:33 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
2014-05-03 12:56 ` James Denholm
2014-05-03 19:22 ` Felipe Contreras [this message]
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=5365420874947_27397d32f016@nysa.notmuch \
--to=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=mmogilvi_git@miniinfo.net \
--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).