From: Jeff King <peff@peff.net>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Caleb Cushing <xenoterracide@gmail.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: Fwd: git status options feature suggestion
Date: Sun, 12 Oct 2008 04:26:08 -0400 [thread overview]
Message-ID: <20081012082607.GA17852@sigill.intra.peff.net> (raw)
In-Reply-To: <20081012044900.GA27845@coredump.intra.peff.net>
On Sun, Oct 12, 2008 at 12:49:00AM -0400, Jeff King wrote:
> A week or two ago I came across yet another git-status annoyance: it
> needs write access to the repository to run (I was helping somebody with
> a task on a shared box, and I wanted to run status in their repository
> using my account).
>
> I considered submitting a patch to fix this, but I think it is really
> more fundamental. I use status to get an overview of what's going on in
> a repo, but it is intimately related to a potential commit.
BTW, in case anybody is interested, here is the patch. Like I said, I
think we are better off with an alternative to "status", but maybe this
is useful to somebody anyway.
---
diff --git a/builtin-commit.c b/builtin-commit.c
index b01ad9f..8951364 100644
--- a/builtin-commit.c
+++ b/builtin-commit.c
@@ -217,7 +217,8 @@ static void create_base_index(void)
exit(128); /* We've already reported the error, finish dying */
}
-static char *prepare_index(int argc, const char **argv, const char *prefix)
+static char *prepare_index(int argc, const char **argv, const char *prefix,
+ int status_only)
{
int fd;
struct string_list partial;
@@ -270,7 +271,13 @@ static char *prepare_index(int argc, const char **argv, const char *prefix)
* We still need to refresh the index here.
*/
if (!pathspec || !*pathspec) {
- fd = hold_locked_index(&index_lock, 1);
+ fd = hold_locked_index(&index_lock, 0);
+ if (fd < 0) {
+ if (!status_only)
+ die("unable to lock index: %s",
+ strerror(errno));
+ return get_index_file();
+ }
refresh_cache(REFRESH_QUIET);
if (write_cache(fd, active_cache, active_nr) ||
commit_locked_index(&index_lock))
@@ -869,7 +876,7 @@ int cmd_status(int argc, const char **argv, const char *prefix)
argc = parse_and_validate_options(argc, argv, builtin_status_usage, prefix);
- index_file = prepare_index(argc, argv, prefix);
+ index_file = prepare_index(argc, argv, prefix, 1);
commitable = run_status(stdout, index_file, prefix, 0);
@@ -953,7 +960,7 @@ int cmd_commit(int argc, const char **argv, const char *prefix)
argc = parse_and_validate_options(argc, argv, builtin_commit_usage, prefix);
- index_file = prepare_index(argc, argv, prefix);
+ index_file = prepare_index(argc, argv, prefix, 0);
/* Set up everything for writing the commit object. This includes
running hooks, writing the trees, and interacting with the user. */
next prev parent reply other threads:[~2008-10-12 8:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 5:34 git status options feature suggestion Caleb Cushing
2008-10-09 6:11 ` Jeff King
[not found] ` <81bfc67a0810082327p421ca4e9v84f4b33023bc6fe6@mail.gmail.com>
2008-10-09 6:27 ` Fwd: " Caleb Cushing
2008-10-09 9:03 ` Johannes Schindelin
2008-10-09 15:12 ` Michael J Gruber
2008-10-10 2:20 ` Caleb Cushing
2008-10-10 4:25 ` Elijah Newren
2008-10-10 11:13 ` Johannes Schindelin
2008-10-12 4:49 ` Jeff King
2008-10-12 6:41 ` Junio C Hamano
2008-10-12 6:45 ` Jeff King
2008-10-12 8:10 ` Junio C Hamano
2008-10-13 1:04 ` Jeff King
2008-10-13 1:30 ` Shawn O. Pearce
2008-10-26 1:47 ` Junio C Hamano
2008-10-26 4:59 ` Jeff King
2008-10-12 18:05 ` Shawn O. Pearce
2008-10-13 1:06 ` Jeff King
2008-10-12 9:07 ` Jakub Narebski
2008-10-12 10:47 ` Wincent Colaiuta
2008-10-12 11:40 ` Teemu Likonen
2008-10-12 13:52 ` Andreas Ericsson
2008-10-12 8:26 ` Jeff King [this message]
2008-10-12 9:58 ` Fwd: " Junio C Hamano
2008-10-13 0:59 ` Jeff King
2008-10-09 21:23 ` ls-files [Was: Re: Fwd: git status options feature suggestion] James Cloos
2008-10-09 21:41 ` Shawn O. Pearce
2008-10-09 22:13 ` Jeremy Ramer
2008-10-09 22:52 ` ls-files James Cloos
-- strict thread matches above, loose matches on Subject: below --
2008-10-12 10:09 Fwd: git status options feature suggestion Leo Razoumov
2008-10-18 0:19 ` Fyn Fynn
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=20081012082607.GA17852@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=xenoterracide@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).