From: Nicolas Pitre <nico@cam.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Marco Costalba <mcostalba@gmail.com>,
Junio C Hamano <junkio@cox.net>, GIT list <git@vger.kernel.org>
Subject: Re: 'git status' is not read-only fs friendly
Date: Sat, 10 Feb 2007 10:54:27 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0702101049480.1757@xanadu.home> (raw)
In-Reply-To: <Pine.LNX.4.63.0702101554170.22628@wbgn013.biozentrum.uni-wuerzburg.de>
On Sat, 10 Feb 2007, Johannes Schindelin wrote:
> So, what is the big problem about accepting that patching git-status for
> one obscure use is wrong, wrong, wrong, when git-diff already does what is
> needed???
Because git-status itself is conceptually a read-only operation, and
having it barf on a read-only file system is justifiably a bug.
But I agree that attempting to fix it now is probably just too risky not
to compromize the 1.5.0 release. Better leave it as a known issue for
v1.5.0 and fix it later... especially if there is a possible workaround
in the mean time.
Nicolas
next prev parent reply other threads:[~2007-02-10 15:54 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
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 [this message]
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=Pine.LNX.4.64.0702101049480.1757@xanadu.home \
--to=nico@cam.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=mcostalba@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).