From: Johannes Sixt <j6t@kdbg.org>
To: "Sérgio Basto" <sergio@serjux.com>, git@vger.kernel.org
Subject: Re: bug report on update-index --assume-unchanged
Date: Fri, 05 Dec 2014 07:55:33 +0100 [thread overview]
Message-ID: <548156E5.2080006@kdbg.org> (raw)
In-Reply-To: <1417759955.10992.2.camel@segulix>
Am 05.12.2014 07:12, schrieb Sérgio Basto:
> Hi,
>
> I add 2 files that I want ignore on commits
> git update-index --assume-unchanged configurations/local.defs
> git update-index --assume-unchanged processor/default.defs
>
> git diff -a
> is clean
> git diff .
> is clean
> git commit -a
>
> nothing added to commit
>
> but
>
> git commit .
> # Changes to be committed:
> # modified: configurations/local.defs
> # modified: processor/default.defs
>
> this is a bug .
Actually, it's a user error. When you set --assume-unchanged, then you
give a promise to git that you do not change the files, and git does not
have to check itself whether there is a change.
But since you did not keep your promise, you get what you deserve. ;-)
So, to follow-up on your nearby post: --assume-unchanged is *not* a tool
to avoid accidentally committing changes to files that are tracked.
-- Hannes
next prev parent reply other threads:[~2014-12-05 6:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 22:42 GIT: ignoring changes in tracked files and bug report Sérgio Basto
2014-12-05 6:12 ` bug report on update-index --assume-unchanged Sérgio Basto
2014-12-05 6:55 ` Johannes Sixt [this message]
2014-12-05 10:52 ` Duy Nguyen
2014-12-05 16:57 ` Sérgio Basto
2014-12-05 18:30 ` Junio C Hamano
2014-12-05 20:48 ` Philip Oakley
2014-12-05 21:05 ` Junio C Hamano
2014-12-05 21:55 ` Philip Oakley
2014-12-05 22:18 ` Andreas Schwab
2014-12-06 0:45 ` Sérgio Basto
2014-12-06 13:28 ` Philip Oakley
2014-12-05 21:19 ` Junio C Hamano
2014-12-05 21:39 ` Sérgio Basto
2014-12-05 21:52 ` Junio C Hamano
2014-12-05 18:33 ` Junio C Hamano
2014-12-05 10:56 ` [PATCH] commit: ignore assume-unchanged files in "commmit <file>" mode Nguyễn Thái Ngọc Duy
2014-12-09 2:44 ` Sérgio Basto
2014-12-11 23:23 ` Philip Oakley
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=548156E5.2080006@kdbg.org \
--to=j6t@kdbg.org \
--cc=git@vger.kernel.org \
--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.
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).