From: Junio C Hamano <junkio@cox.net>
To: "Marco Costalba" <mcostalba@gmail.com>
Cc: "Junio C Hamano" <junkio@cox.net>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"GIT list" <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] run_diff_{files,index}(): update calling convention.
Date: Sat, 10 Feb 2007 00:20:59 -0800 [thread overview]
Message-ID: <7vps8imnis.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <e5bfff550702100002y3929c50mfb99b8da44c9c82b@mail.gmail.com> (Marco Costalba's message of "Sat, 10 Feb 2007 09:02:15 +0100")
"Marco Costalba" <mcostalba@gmail.com> writes:
> Running 'git runstatus' alone shows _all_ the repo files, although are
> not modified and not touched.
That does not sound right with or without my patch. Are you
talking about the 'git runstatus' with my patch is showing
paths that are cache clean? If that is the case that means my
patch is introudcing regression.
next prev parent reply other threads:[~2007-02-10 8:21 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 19:25 'git status' is not read-only fs friendly Marco Costalba
2007-02-09 19:56 ` Linus Torvalds
2007-02-09 20:19 ` Marco Costalba
2007-02-09 20:27 ` Junio C Hamano
2007-02-09 20:22 ` Junio C Hamano
2007-02-09 20:29 ` Morten Welinder
2007-02-09 23:27 ` Theodore Tso
2007-02-09 20:35 ` Marco Costalba
2007-02-09 20:59 ` Linus Torvalds
2007-02-10 0:12 ` Junio C Hamano
2007-02-10 0:16 ` Junio C Hamano
2007-02-10 2:51 ` [PATCH 1/2] run_diff_{files,index}(): update calling convention Junio C Hamano
2007-02-10 8:02 ` Marco Costalba
2007-02-10 8:20 ` Junio C Hamano [this message]
2007-02-10 8:29 ` Marco Costalba
2007-02-10 8:46 ` Marco Costalba
2007-02-10 10:40 ` Junio C Hamano
2007-02-10 11:25 ` Marco Costalba
2007-02-10 15:13 ` Junio C Hamano
2007-02-10 15:51 ` Marco Costalba
2007-02-10 2:51 ` [PATCH 2/2] git-runstatus --refresh Junio C Hamano
2007-02-10 14:19 ` 'git status' is not read-only fs friendly Johannes Schindelin
2007-02-10 14:31 ` Marco Costalba
2007-02-10 14:41 ` Johannes Schindelin
2007-02-10 14:48 ` Marco Costalba
2007-02-10 14:51 ` Marco Costalba
2007-02-10 16:25 ` Junio C Hamano
2007-02-10 20:36 ` Johannes Schindelin
2007-02-11 21:57 ` Junio C Hamano
2007-02-11 22:09 ` Johannes Schindelin
2007-02-11 22:28 ` Johannes Schindelin
2007-02-11 22:30 ` Junio C Hamano
2007-02-11 23:24 ` Johannes Schindelin
2007-02-10 14:59 ` Johannes Schindelin
2007-02-10 15:45 ` Marco Costalba
2007-02-10 15:54 ` Nicolas Pitre
2007-02-10 16:27 ` Junio C Hamano
2007-02-10 16:40 ` Nicolas Pitre
2007-02-10 16:46 ` Junio C Hamano
2007-02-10 17:03 ` Nicolas Pitre
2007-02-10 18:00 ` Junio C Hamano
2007-02-10 18:43 ` Theodore Tso
2007-02-10 18:53 ` Nicolas Pitre
2007-02-10 18:56 ` Theodore Tso
2007-02-10 19:08 ` Marco Costalba
2007-02-10 17:37 ` Linus Torvalds
2007-02-10 18:51 ` Nicolas Pitre
2007-02-11 6:33 ` Junio C Hamano
2007-02-11 7:23 ` Shawn O. Pearce
2007-02-10 20:40 ` Johannes Schindelin
2007-02-10 16:25 ` Junio C Hamano
2007-02-10 16:35 ` Marco Costalba
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=7vps8imnis.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mcostalba@gmail.com \
--cc=torvalds@linux-foundation.org \
/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.