All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.8.0-rc0
Date: Sat, 27 Feb 2016 09:46:42 -0800	[thread overview]
Message-ID: <xmqqtwkugi65.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CAP8UFD0XF=tx0RAu+uH20UpGm45HPrcxSBJZEGKc4xiOro1jvA@mail.gmail.com> (Christian Couder's message of "Sat, 27 Feb 2016 12:10:08 +0100")

Christian Couder <christian.couder@gmail.com> writes:

> On Sat, Feb 27, 2016 at 12:41 AM, Junio C Hamano <gitster@pobox.com> wrote:
>>
>> Git 2.8 Release Notes (draft)
>> =============================
>>
>> Backward compatibility note
>> ---------------------------
>>
>> The rsync:// transport has been removed.
>
> We may want to add something about untracked cache changes here, maybe
> something like:
>
>     The untracked cache subsystem has been updated and its primary UI
> has been changed
>     from "git update-index" to "git config" with some small backward
> incompatibilities.

I seriously hope we do not have to do that, and you do too.

The section is about "We deliberately did something that breaks your
expectation", "You may have been assuming that X would be a good way
to achieve Y, but X no longer will serve that purpose".  The latter
can be optionally followed by "To do Y, you now can do W instead",
but it still is breaking the established way of using Git.

I did not think your untracked update was done in such a way to
"break" existing uses (if it is not the case and breaks existing
uses, it needs to be fixed, but I think we made sure it will keep
working the same way for those who do not explicitly set
configuration to adopt the new behaviour).

  reply	other threads:[~2016-02-27 17:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26 23:41 [ANNOUNCE] Git v2.8.0-rc0 Junio C Hamano
2016-02-27 11:10 ` Christian Couder
2016-02-27 17:46   ` Junio C Hamano [this message]
2016-02-29  9:24 ` Sebastian Schuberth

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=xmqqtwkugi65.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    /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.