From: Matthew McClure <matt@continuousdelta.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: How to track history of personal changes in a repository?
Date: Tue, 3 Sep 2019 08:57:15 -0400 [thread overview]
Message-ID: <CAEV-cEr1tHc4zY7hYSUVUFcqO60y1ssXHC1jO20606HzB4QxnA@mail.gmail.com> (raw)
In-Reply-To: <2737a9f3-769d-5dc7-ca4e-ef4dbdde70f6@iee.email>
On Sat, Aug 31, 2019 at 09:32 Philip Oakley <philipoakley@iee.email> wrote:
>
>
> The `assume-unchanged bit` is commonly miss-construed as a promise by
> Git that it will ignore changes to the file.
Maybe `--skip-worktree` would be more appropriate.
prev parent reply other threads:[~2019-09-03 12:57 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
2019-09-03 12:57 ` Matthew McClure [this message]
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=CAEV-cEr1tHc4zY7hYSUVUFcqO60y1ssXHC1jO20606HzB4QxnA@mail.gmail.com \
--to=matt@continuousdelta.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.
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).