git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: greened@obbligato.org
To: Herman van Rink <rink@initfour.nl>
Cc: git@vger.kernel.org, apenwarr@gmail.com
Subject: Re: git-subtree recent contributions
Date: Sun, 01 Apr 2012 13:07:37 -0500	[thread overview]
Message-ID: <87iphj497a.fsf@smith.obbligato.org> (raw)
In-Reply-To: <4F7562AD.1040303@initfour.nl> (Herman van Rink's message of "Fri, 30 Mar 2012 09:37:17 +0200")

Herman van Rink <rink@initfour.nl> writes:

> Hi,
>
> I'm glad to see some interest here to merge git-subtree into git.git.
>
> Related to that I would like to draw your attention to a fork of mine on
> github.
> I've recently spent some time to pull many contributions to git-subtree
> together.

Thanks!  I'll have a look at these.  In the meantime, we'll get
git-subtree merged after the next release and then we can look at
applying these patches.

Sound good?

                                  -Dave

  reply	other threads:[~2012-04-01 18:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-30  7:37 git-subtree recent contributions Herman van Rink
2012-04-01 18:07 ` greened [this message]
2012-04-02  7:44   ` Herman van Rink

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=87iphj497a.fsf@smith.obbligato.org \
    --to=greened@obbligato.org \
    --cc=apenwarr@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=rink@initfour.nl \
    /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).