From: Rogan Dawes <discard@dawes.za.net>
To: Pazu <pazu@pazu.com.br>
Cc: git@vger.kernel.org
Subject: Re: Ignoring local changes
Date: Thu, 14 Dec 2006 23:27:48 +0200 [thread overview]
Message-ID: <4581C1D4.7080102@dawes.za.net> (raw)
In-Reply-To: <9e7ab7380612140855p1f4ee6c1l5ef24c4d1d169da6@mail.gmail.com>
Pazu wrote:
> 2006/12/14, Andreas Ericsson <ae@op5.se>:
>
>> Correction: I just tested this, and while git-add won't touch the file,
>> git-update-index will, and git-status still shows it as modified.
>
> Yes, and that's exactly my problems. There are a number of
> modified/removed files in my working copy that were previously added
> to the repository, and git-status shows them as modified/removed, even
> when they're listed in .gitignore or .git/info/exclude
>
>> This feels like a bug to me.
>
> Dunno, sounds like this is by design. I acknowledge that my situation
> is unusual, and most often, you'll want to always track a file once
> it's been added to the repository.
>
> -- Pazu
Why not remove it from the repo, then set .gitignore?
If it is generated code, or compiled code, it probably shouldn't be in
the repo in the first place . . . Simply correct that mistake, and you
are good to go.
next prev parent reply other threads:[~2006-12-14 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 16:26 Ignoring local changes Pazu
2006-12-14 16:44 ` Andreas Ericsson
2006-12-14 16:55 ` Pazu
2006-12-14 21:27 ` Rogan Dawes [this message]
2006-12-14 21:36 ` Pazu
2006-12-14 21:56 ` Pazu
2006-12-15 0:15 ` Johannes Schindelin
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=4581C1D4.7080102@dawes.za.net \
--to=discard@dawes.za.net \
--cc=git@vger.kernel.org \
--cc=pazu@pazu.com.br \
/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).