From: Johannes Sixt <j6t@kdbg.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2013, #04; Thu, 15)
Date: Sun, 18 Aug 2013 13:46:55 +0200 [thread overview]
Message-ID: <5210B42F.7050106@kdbg.org> (raw)
In-Reply-To: <7vbo4ypon7.fsf@alter.siamese.dyndns.org>
Am 16.08.2013 00:36, schrieb Junio C Hamano:
> Due to unfortunate regressions, two topics had to be reverted:
>
> * An attempted fix to "git stash save", to detect that going back
> to the state of the HEAD needs to lose killed files, and/or
> untracked files in a killed directory, to prevent the command
> from proceeding without "--force".
>
> This used "ls-files -k" that was unusably slow.
>
> * An attempted enhancement to allow "@" to be used to name "HEAD".
>
> This rewrote "@" in a ref where it shouldn't have,
> e.g. refs/@/foo.
You still need to remove corresponding paragraphs from the release notes.
-- Hannes
next prev parent reply other threads:[~2013-08-18 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 22:36 What's cooking in git.git (Aug 2013, #04; Thu, 15) Junio C Hamano
2013-08-18 11:46 ` Johannes Sixt [this message]
2013-08-19 16:53 ` 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=5210B42F.7050106@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).