git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Marco Craveiro <marco.craveiro@gmail.com>
To: Andrew Ardill <andrew.ardill@gmail.com>
Cc: Sitaram Chamarty <sitaramc@gmail.com>,
	demerphq <demerphq@gmail.com>,
	pascal@obry.net, git@vger.kernel.org
Subject: Re: Ignore on commit
Date: Fri, 5 Oct 2012 07:09:05 +0100	[thread overview]
Message-ID: <CAKRNd4w1LPEBxhfRNzSwwFDQen_Sif+EYQXcAxnJPP6GU-Q5nw@mail.gmail.com> (raw)
In-Reply-To: <CAH5451ki_JFntWZwxcUqvWKwZn62Vfg=MkF3xwiX1p3ARULQfA@mail.gmail.com>

<git update-index --assume-unchanged>
> From the help page:
>
> --assume-unchanged, --no-assume-unchanged
>     ...
>
>     This option can be also used as a coarse file-level mechanism to
> ignore uncommitted changes in tracked files (akin to what .gitignore
>     does for untracked files).
>
> Seems like it does everything required. I tested and it correctly
> hides changes that I want hidden. The only thing I can't see how to do
> is get git status to show files with the assume unchanged  bit set. I
> think there is no way currently, but that might be a nice addition to
> make the initial request feature complete. It could show either all
> files with the bit set, or files with the bit set that have been
> changed (or this could be configurable).

This is indeed the solution outlined in [4] on my original post:

http://gitready.com/intermediate/2009/02/18/temporarily-ignoring-files.html

The presence in git status is quite important or else one has to
change the regular workflow with a second status command.

Cheers

Marco
-- 
So young, and already so unknown -- Pauli

blog: http://mcraveiro.blogspot.com

  reply	other threads:[~2012-10-05  7:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-04 16:45 Ignore on commit Marco Craveiro
2012-10-04 20:06 ` Pascal Obry
2012-10-04 21:20   ` Marco Craveiro
2012-10-04 23:02     ` Andrew Wong
2012-10-05  1:00     ` Andrew Ardill
2012-10-05  1:35       ` demerphq
2012-10-05  2:20         ` Sitaram Chamarty
2012-10-05  2:44           ` Junio C Hamano
2012-10-05  2:44           ` Andrew Ardill
2012-10-05  6:09             ` Marco Craveiro [this message]
2012-10-05  7:00       ` Philip Oakley
2012-10-05 13:30     ` Pascal Obry

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=CAKRNd4w1LPEBxhfRNzSwwFDQen_Sif+EYQXcAxnJPP6GU-Q5nw@mail.gmail.com \
    --to=marco.craveiro@gmail.com \
    --cc=andrew.ardill@gmail.com \
    --cc=demerphq@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pascal@obry.net \
    --cc=sitaramc@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).