From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-multimail: update to version 1.0.0
Date: Wed, 09 Apr 2014 09:35:40 -0700 [thread overview]
Message-ID: <xmqqwqey1mw3.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <53456EC8.7090109@alum.mit.edu> (Michael Haggerty's message of "Wed, 09 Apr 2014 18:01:12 +0200")
Michael Haggerty <mhagger@alum.mit.edu> writes:
>> In the longer term, I have a feeling that we may be better off to
>> make the "git core" tree not be the "batteris included" convenience
>> tree, though....
> ...
> Tell me if/when you want to transition to omitting git-multimail (and
> presumably post-receive-email and maybe others) from the Git source
> tree. I suppose in that case we would replace the scripts with pointers
> to where they can be obtained.
Yes, that would be a longer-term thing, not related to this "one
round of periodical updates" patch. I do not have any specific
timeframe in mind at this moment.
prev parent reply other threads:[~2014-04-09 16:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 15:20 [PATCH] git-multimail: update to version 1.0.0 Michael Haggerty
2014-04-07 18:56 ` Junio C Hamano
2014-04-09 16:01 ` Michael Haggerty
2014-04-09 16:35 ` 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=xmqqwqey1mw3.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
/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).