From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Michael Haggerty <mhagger@alum.mit.edu>, git@vger.kernel.org
Subject: Re: [PATCH] Update git-multimail to version 1.0.2
Date: Mon, 27 Apr 2015 21:20:31 +0200 [thread overview]
Message-ID: <vpqa8xtpedc.fsf@anie.imag.fr> (raw)
In-Reply-To: <xmqqfv7lwfvx.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Mon, 27 Apr 2015 12:05:54 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Hmm, that may be technically correct but it is grossly misleading to
> update the existing "was obtained on 2014-04-07" to "was obtained on
> 2015-04-27", especially if nothing was actually obtained, isn't it?
That is because you're looking at the patch. The intended audience are
people reading the README.Git file, and the text reads just fine then.
> I honestly am surprised that, after seeing the announcement about "a
> new repository, co-maintainer and multiple contributors", no code
> change is made over the past 12 months.
That is the point indeed. Michael does not use git-multimail himself,
and does not find time to work on it. I'm joining the effort, but
currently have no time either. But eventually I'll go through the list
of pending pull-requests, and we'll actually get new code.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2015-04-27 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 11:17 [PATCH] Update git-multimail to version 1.0.2 Michael Haggerty
2015-04-27 11:29 ` Matthieu Moy
2015-04-27 17:50 ` Junio C Hamano
2015-04-27 18:18 ` Matthieu Moy
2015-04-27 18:25 ` Junio C Hamano
2015-04-27 18:41 ` Matthieu Moy
2015-04-27 18:44 ` Junio C Hamano
2015-04-27 18:54 ` Matthieu Moy
2015-04-27 19:05 ` Junio C Hamano
2015-04-27 19:20 ` Matthieu Moy [this message]
2015-04-27 20:05 ` Michael Haggerty
2015-04-28 7:20 ` Junio C Hamano
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=vpqa8xtpedc.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).