git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: A Large Angry SCM <gitzilla@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	Alexander Gladysh <agladysh@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH/RFC] gitk: refresh index before checking for local changes
Date: Wed, 07 Apr 2010 07:21:53 -0400	[thread overview]
Message-ID: <4BBC6AD1.80202@gmail.com> (raw)
In-Reply-To: <7vfx37g6f6.fsf@alter.siamese.dyndns.org>

Junio C Hamano wrote:
> A Large Angry SCM <gitzilla@gmail.com> writes:
> 
>> NAK - gitk should not modify a repository and/or working dir unless
>> _explicitly_ prompted to by the user.
> 
> I used to think that way, until I realized that gitk has operations like
> "Tag this commit" that does write into the repository.
> 

Does that happen every time you run gitk or only when the gitk user 
instructs gitk to?

  reply	other threads:[~2010-04-07 11:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 22:57 gitk pays too much attention to file timestamps Alexander Gladysh
2010-04-06 23:15 ` Markus Heidelberg
2010-04-06 23:36 ` Jonathan Nieder
2010-04-06 23:47   ` Alexander Gladysh
2010-04-07  0:43     ` [PATCH/RFC] gitk: refresh index before checking for local changes Jonathan Nieder
2010-04-07  1:07       ` Alexander Gladysh
2010-04-07  1:16       ` Jonathan Nieder
2010-04-07  2:21       ` A Large Angry SCM
2010-04-07  2:57         ` Jonathan Nieder
2010-04-07  5:47         ` Junio C Hamano
2010-04-07 11:21           ` A Large Angry SCM [this message]
2010-04-07 16:48           ` Avery Pennarun
2010-04-07 14:36         ` Jon Seymour
2010-04-06 23:58   ` gitk pays too much attention to file timestamps Avery Pennarun
2010-04-07  1:01     ` Jonathan Nieder

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=4BBC6AD1.80202@gmail.com \
    --to=gitzilla@gmail.com \
    --cc=agladysh@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@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).