From: "Philip Oakley" <philipoakley@iee.org>
To: "Andrew Ardill" <andrew.ardill@gmail.com>,
"Marco Craveiro" <marco.craveiro@gmail.com>
Cc: <pascal@obry.net>, <git@vger.kernel.org>
Subject: Re: Ignore on commit
Date: Fri, 5 Oct 2012 08:00:12 +0100 [thread overview]
Message-ID: <5DB4E90436854A219805224B2C375CC9@PhilipOakley> (raw)
In-Reply-To: CAH5451mpJw4+noUF+FkZJS+Y2oq2ThFeG7wSOCdbVaMQPNgUJA@mail.gmail.com
From: "Andrew Ardill" <andrew.ardill@gmail.com>
> On 5 October 2012 07:20, Marco Craveiro <marco.craveiro@gmail.com>
> wrote:
>> ...
>> Similar but not quite; the idea is that you know that there is some
>> code (I'm just talking about files here, so lets ignore hunks for the
>> moment) which is normally checked in but for a period of time you
>> want
>> it ignored. So you don't want it git ignored but at the same time you
>> don't want to see these files in the list of modified files.
>
> What is the reason git ignore is no good in this case? Is it simply
> that you can't see the ignored files in git status, or is it that
> adding and removing entries to .gitignore is too cumbersome? If it's
> the latter you could probably put together a simple shell wrapper to
> automate the task, as otherwise it seems like git ignore does what you
> need.
>
IIUC the files are already tracked, and a variant of ' git
update-index --assume-unchanged' is being requested, so that the command
doesn't need to be repeated if they checkuout / swap branches (which
assumes I've understood the effect of such an index change correctly)
> Regards,
>
> Andrew Ardill
> --
next prev parent reply other threads:[~2012-10-05 7:00 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
2012-10-05 7:00 ` Philip Oakley [this message]
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=5DB4E90436854A219805224B2C375CC9@PhilipOakley \
--to=philipoakley@iee.org \
--cc=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=marco.craveiro@gmail.com \
--cc=pascal@obry.net \
/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).