All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan del Strother <maillist@steelskies.com>,
	Johannes Sixt <j.sixt@viscovery.net>,
	git@vger.kernel.org, Nanako Shiraishi <nanako3@lavabit.com>
Subject: Re: Re*: Peculiar behavior of git 1.5.6
Date: Thu, 04 Sep 2008 11:05:37 -0500	[thread overview]
Message-ID: <48C00751.3030102@lwfinger.net> (raw)
In-Reply-To: <7v3akg5jul.fsf_-_@gitster.siamese.dyndns.org>

Junio C Hamano wrote:
> 
> But pull to merge codepath in question that Larry originally brought up
> always did, and that is what puzzles me.
> 
> Perhaps some virus scanner or trackerd is running under Larry's working
> tree that contaminates the stat information after we refresh the index?  I
> dunno.

No, neither a virus scanner nor trackerd are running.

I use quilt to handle my local patches. One of the things that I have 
found confusing is that sometimes git complains about the files that 
have been restored, and sometimes not.

I replaced git on the machine in question with the latest git version 
(1.6.0.1.216.g1b23a) so the behavior will be the latest.

Thanks for the answers,

Larry

      parent reply	other threads:[~2008-09-04 16:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04  5:43 Peculiar behavior of git 1.5.6 Larry Finger
2008-09-04  8:09 ` Johannes Sixt
2008-09-04  8:35   ` Junio C Hamano
2008-09-04  9:11     ` Jonathan del Strother
2008-09-04  9:41       ` Re*: " Junio C Hamano
2008-09-04 10:20         ` Nanako Shiraishi
2008-09-04 16:05         ` Larry Finger [this message]

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=48C00751.3030102@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j.sixt@viscovery.net \
    --cc=maillist@steelskies.com \
    --cc=nanako3@lavabit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.