git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Emily Xie <emilyxxie@gmail.com>,
	git@vger.kernel.org, novalis@novalis.org
Subject: Re: [PATCH] pathspec: die on empty strings as pathspec
Date: Sat, 10 Jun 2017 20:03:16 +0900	[thread overview]
Message-ID: <xmqqvao414wb.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170610062151.fv7d4audrwav2hy3@sigill.intra.peff.net> (Jeff King's message of "Sat, 10 Jun 2017 02:21:51 -0400")

Jeff King <peff@peff.net> writes:

> That's long enough for people who actually ran the intermediate
> versions.  But what about people on distros who jump from v2.10 or lower
> straight to v2.14?
>
> I think to catch them we'd literally need years on our deprecation
> schedules. Maybe it's not worth caring about. That's an awful long time
> for people who _are_ upgrading each version to see the warning. Of
> course the end game in this case is that it becomes an error, so they'll
> be notified either way. :)
>
> I'm OK with this case being a relatively quick deprecation, but your
> "long enough" made me wonder how we would decide that.
>
> -Peff
>
> [1] Debian stable is set to release in a week or so. People doing that
>     stable upgrade will go from v2.1.4 to v2.11.0. So they won't
>     actually skip the deprecation notice, but they'll probably live with
>     the warning for 3 years or so.

Yuck X-<.

  reply	other threads:[~2017-06-10 11:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07  3:33 [PATCH] pathspec: die on empty strings as pathspec Emily Xie
2017-06-09 16:28 ` Junio C Hamano
2017-06-10  6:21   ` Jeff King
2017-06-10 11:03     ` Junio C Hamano [this message]
2017-06-09 16:50 ` Brandon Williams
2017-06-10  5:54 ` Junio C Hamano
2017-06-23  2:34   ` Emily Xie
2017-06-23  4:09     ` Junio C Hamano
2017-06-23  4:46       ` Junio C Hamano
2017-06-23 18:04         ` Junio C Hamano
2017-06-23 20:52           ` Torsten Bögershausen
2017-06-23 20:59             ` 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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqvao414wb.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=emilyxxie@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=novalis@novalis.org \
    --cc=peff@peff.net \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).