From: Philip Oakley <philipoakley@iee.email>
To: Elijah Newren <newren@gmail.com>,
Matthew McClure <matt@continuousdelta.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: How to track history of personal changes in a repository?
Date: Sat, 31 Aug 2019 14:32:28 +0100 [thread overview]
Message-ID: <2737a9f3-769d-5dc7-ca4e-ef4dbdde70f6@iee.email> (raw)
In-Reply-To: <CABPp-BEWn1wHdxWM8cVqmvzYo8HDdUzuh4G-XTN51o8JdvkrCw@mail.gmail.com>
Hi Elijah, Matt
On 30/08/2019 16:21, Elijah Newren wrote:
> * If the changes are to files that are tracked, AND you aren't making
> changes to those same files that do need to be committed and pushed,
> use the assume-unchanged bit (see git-update-index(1)).
Not sure I parsed that well but...
The `assume-unchanged bit` is commonly miss-construed as a promise by
Git that it will ignore changes to the file.
That is incorrect. The bit is a promise by the _user_ that they won't
change the file, so that, in general Git stops checking for updates to
the file.
However it will check for updates sometimes, leading to unexpected
effects if the user has the wrong mental model, thinking that Git would
ignore their changes...
Philip
next prev parent reply other threads:[~2019-08-31 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 14:32 How to track history of personal changes in a repository? Matthew McClure
2019-08-29 17:04 ` Elijah Newren
2019-08-29 17:55 ` Matthew McClure
2019-08-30 15:21 ` Elijah Newren
2019-08-31 13:32 ` Philip Oakley [this message]
2019-09-03 12:57 ` Matthew McClure
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=2737a9f3-769d-5dc7-ca4e-ef4dbdde70f6@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
--cc=matt@continuousdelta.com \
--cc=newren@gmail.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).