From: "Philip Oakley" <philipoakley@iee.org>
To: "Sérgio Basto" <sergio@serjux.com>
Cc: "GitList" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>,
"Duy Nguyen" <pclouds@gmail.com>, "Johannes Sixt" <j6t@kdbg.org>,
"Michael J Gruber" <git@drmicha.warpmail.net>
Subject: Re: [PATCH v2] doc: make clear --assume-unchanged's user contract
Date: Tue, 9 Dec 2014 08:13:16 -0000 [thread overview]
Message-ID: <CD806F4871C843B399611747A4B57035@PhilipOakley> (raw)
In-Reply-To: 39592B1FCE234EA58078EBFB34171859@PhilipOakley
From: "Philip Oakley" <philipoakley@iee.org>
> From: "Sérgio Basto" <sergio@serjux.com>
>> On Sáb, 2014-12-06 at 15:04 +0000, Philip Oakley wrote:
>>> Many users misunderstand the --assume-unchanged contract, believing
>>> it means Git won't look at the flagged file.
[...]
> retrospect, so my patch seeks to clarify the existing situation. That
> is "please git, update the index, you can assume these files are
> unchanged ... ".
... and if you don't trust me, then you can even go and check
[Honestly, you can trust me I'm a developer]"
--
the extra bit.
Philip
next prev parent reply other threads:[~2014-12-09 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 15:04 [PATCH v2] Improve --assume-unchanged in the git update-index man page Philip Oakley
2014-12-06 15:04 ` [PATCH v2] doc: make clear --assume-unchanged's user contract Philip Oakley
2014-12-09 3:43 ` Sérgio Basto
2014-12-09 7:59 ` Philip Oakley
2014-12-09 8:13 ` Philip Oakley [this message]
2014-12-09 8:30 ` Michael J Gruber
2014-12-09 11:13 ` [PATCH] gitignore.txt: do not suggest assume-unchanged Michael J Gruber
2014-12-10 1:06 ` Jonathan Nieder
2014-12-11 15:13 ` Michael J Gruber
2014-12-10 0:44 ` [PATCH v2] doc: make clear --assume-unchanged's user contract Junio C Hamano
2014-12-10 1:49 ` Sérgio Basto
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=CD806F4871C843B399611747A4B57035@PhilipOakley \
--to=philipoakley@iee.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=pclouds@gmail.com \
--cc=sergio@serjux.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