From: Junio C Hamano <gitster@pobox.com>
To: Stefan Beller <sbeller@google.com>
Cc: Duy Nguyen <pclouds@gmail.com>, Antonio Ospite <ao2@ao2.it>,
git <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Aug 2018, #04; Fri, 17)
Date: Mon, 20 Aug 2018 14:32:34 -0700 [thread overview]
Message-ID: <xmqq6004bu6l.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CAGZ79kbQ5L39kdsfouPXJjJOm_Ni9TY5Qan7nHZE9VbcaEMyGA@mail.gmail.com> (Stefan Beller's message of "Mon, 20 Aug 2018 11:11:25 -0700")
Stefan Beller <sbeller@google.com> writes:
>> I find the design a bit iffy in that our usual "missing in the
>> working tree? let's use the latest blob" fallback is to take it
>> from the index, not from the HEAD.
>
> I am not sure; why does it feel iffy?
Why doesn't it? There is no justification why it has to be
different from others and read from HEAD bypassing index.
next prev parent reply other threads:[~2018-08-20 21:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-17 22:44 What's cooking in git.git (Aug 2018, #04; Fri, 17) Junio C Hamano
2018-08-18 6:29 ` Duy Nguyen
2018-08-18 6:59 ` Jonathan Nieder
2018-08-20 17:26 ` Junio C Hamano
2018-08-20 18:14 ` Derrick Stolee
2018-08-18 9:34 ` Christian Couder
2018-08-18 11:34 ` Ævar Arnfjörð Bjarmason
2018-08-18 12:54 ` Christian Couder
2018-08-18 11:10 ` Ævar Arnfjörð Bjarmason
2018-08-20 10:23 ` Phillip Wood
2018-08-20 17:44 ` Eric Sunshine
2018-08-20 19:36 ` pw/rebase-i-author-script-fix, was " Johannes Schindelin
2018-08-20 18:11 ` Stefan Beller
2018-08-20 21:32 ` Junio C Hamano [this message]
2018-08-20 18:19 ` Jonathan Nieder
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=xmqq6004bu6l.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=ao2@ao2.it \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=sbeller@google.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.
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).