All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Michael Haggerty <mhagger@alum.mit.edu>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>, git@vger.kernel.org
Subject: Re: [PATCH] Update git-multimail to version 1.0.2
Date: Tue, 28 Apr 2015 00:20:02 -0700	[thread overview]
Message-ID: <xmqqfv7kvhwd.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <553E9671.3000902@alum.mit.edu> (Michael Haggerty's message of "Mon, 27 Apr 2015 22:05:05 +0200")

Michael Haggerty <mhagger@alum.mit.edu> writes:

> On 04/27/2015 09:05 PM, Junio C Hamano wrote:
> ...
>> 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?
> ...
> It's true that only documentation changes are in the patch, but it still
> seemed like good practice to create a tag and all that. If nothing else,
> it will make it easier to figure out the baseline for future code drops.

Oh, there is no question about that ;-)

> There have been a couple of small software changes in git-multimail's
> master branch, but I didn't include those in the patch I submitted to
> you because I thought you wouldn't want to have code changes so close to
> the release. So 1.0.2 is on the newly-created "maint" branch.

OK.

>> 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.
>
> I totally understand your disappointment. Mea culpa.

I am not *disappointed* at all.  No recent changes do not
automatically mean abandoned software---it may be a sign of
stability.  I was just *surprised*.

After all, 1.0.2 tag will hopefully soon become stale, and people
have to go to the upstream to see what the latest version is called
anyway, instead of looking at my tree.  So the primary value of
having a copy in my tree is (1) to have the URL for the true
upstream and (2) to have a working version that is not too stale.
So from that point of view, a patch without the update to the
version numbers or datestamps, i.e. just changes the URLs and
updates who to contact, would have been more truthful, unless it
also updated the code.

It was just that the update changed "the last obtained date" without
changing anything of substance that was "obtained" (because there
wasn't anything new to be obtained) and that looked unexpected and
surprised me.  That's all.

      reply	other threads:[~2015-04-28  7: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
2015-04-27 20:05               ` Michael Haggerty
2015-04-28  7:20                 ` 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=xmqqfv7kvhwd.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --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 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.