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 20:54:22 +0200 [thread overview]
Message-ID: <vpq618hqu5d.fsf@anie.imag.fr> (raw)
In-Reply-To: <xmqqk2wxwgv1.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Mon, 27 Apr 2015 11:44:50 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:
>
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> Was that obtained from the upstream project (i.e. you) and match
>>> your 1.0.2 tag?
>>
>> Yes. Isn't that what the text above says?
>
> Well, the patch does not update git_multimail.py at all. Requoting
> the part you omitted from my response
>
> $ git rev-list -1 master contrib/hooks/multimail/
> b513f71f6043c05c3918e670b332dfa7ec6b2661
>
> which is b513f71f (git-multimail: update to version 1.0.0,
> 2014-04-07)
>
> it matches what "was obtained from the upstream project on
> 2014-04-07".
Yes, but it also matches "was obtained on 2015-04-27", since only the
README has changed (the commit message of this patch says: "The only
changes are to the README files, most notably the list of maintainers
and the project URL.").
> Or did you forget to include the update to the software in the
> patch?
The update to the software is empty.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2015-04-27 18:54 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 [this message]
2015-04-27 19:05 ` Junio C Hamano
2015-04-27 19:20 ` Matthieu Moy
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=vpq618hqu5d.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 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.