All of lore.kernel.org
 help / color / mirror / Atom feed
From: greened@obbligato.org (David A. Greene)
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: git-subtree Ready #2
Date: Tue, 14 Feb 2012 23:31:30 -0600	[thread overview]
Message-ID: <87sjicpsr1.fsf@smith.obbligato.org> (raw)
In-Reply-To: <20120215050855.GB29902@sigill.intra.peff.net> (Jeff King's message of "Wed, 15 Feb 2012 00:08:55 -0500")

Jeff King <peff@peff.net> writes:

> On Tue, Feb 14, 2012 at 10:30:16PM -0600, David A. Greene wrote:
>
>> This is also available at:
>> 
>> git clone git://sources.obbligato.org/git/git.git
>
> Hmm. So it seems like a pretty straightforward subtree merge of
> git-subtree. 

Yep.

> I can't say I'm super excited about having copied bits like
> contrib/subtree/t/Makefile that are basically replicas of git's
> t/Makefile.  

I know, I didn't like it either but could not think of a better way.

> But there's not that much of it, the cruft lives in contrib, and
> there's really not a good solution short of actually making
> git-subtree a first-class git command.

That's the conclusion I came to.  Moving it to a first-class command
should be pretty simple when the time comes.

> 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 plan to send patcher to git@vger.  I don't think a pull would be
practical given the removal of redundant files and other things.

                           -Dave

  reply	other threads:[~2012-02-15  5:34 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-11 17:35 git-subtree Ready #2 David A. Greene
2012-02-11 18:03 ` Junio C Hamano
2012-02-11 19:22   ` David A. Greene
2012-02-15  4:30 ` David A. Greene
2012-02-15  5:08   ` Jeff King
2012-02-15  5:31     ` David A. Greene [this message]
2012-02-16  4:07       ` David A. Greene
2012-02-20 19:34         ` David A. Greene
2012-02-20 20:53         ` Jeff King
2012-02-20 23:14           ` Junio C Hamano
2012-02-21  5:37             ` David A. Greene
2012-02-21  6:34               ` Junio C Hamano
2012-02-21  7:10                 ` Junio C Hamano
2012-02-21  8:44                 ` Junio C Hamano
2012-02-21  9:07               ` Thomas Rast
2012-02-24  1:19             ` Avery Pennarun
2012-02-24 20:56               ` Junio C Hamano
2012-02-24 23:57                 ` Avery Pennarun
2012-02-25  5:00                   ` David A. Greene
2012-02-25  9:00                     ` Junio C Hamano
2012-02-25 15:00                       ` David A. Greene
2012-02-27 21:06                         ` Junio C Hamano
2012-02-27 21:21                           ` Jeff King
2012-02-27 21:23                             ` Jeff King
2012-02-28  2:04                             ` Jakub Narebski
2012-02-28 22:42                               ` Avery Pennarun
2012-03-02  3:42                           ` David A. Greene
2012-02-21  5:31           ` David A. Greene

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=87sjicpsr1.fsf@smith.obbligato.org \
    --to=greened@obbligato.org \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.