From: "Sérgio Basto" <sergio@serjux.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Duy Nguyen <pclouds@gmail.com>, Johannes Sixt <j6t@kdbg.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: bug report on update-index --assume-unchanged
Date: Fri, 05 Dec 2014 21:39:50 +0000 [thread overview]
Message-ID: <1417815590.23238.11.camel@segulix> (raw)
In-Reply-To: <xmqq1toeq79b.fsf@gitster.dls.corp.google.com>
On Sex, 2014-12-05 at 10:30 -0800, Junio C Hamano wrote:
> Your promise is "these paths I will not modify" and in return you
> gain performance in "git status"
yeah so --assume-unchanged is for administrators of git , like I write
I change first and --assume-unchanged after and never change it
again .
But if it is a tool for administration of git , I don't what to say ...
put it in a gitadmin command .
I hate git and this is one one the reason .
--
Sérgio M. B.
next prev parent reply other threads:[~2014-12-05 21:40 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1417815590.23238.11.camel@segulix \
--to=sergio@serjux.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j6t@kdbg.org \
--cc=pclouds@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.
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 NNTP newsgroup(s).