From: Joshua Jensen <jjensen@workspacewhiz.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What exactly does 'needs update' mean?
Date: Sat, 25 Sep 2010 08:16:07 -0600 [thread overview]
Message-ID: <4C9E0427.9080901@workspacewhiz.com> (raw)
In-Reply-To: <7vk4manyql.fsf@alter.siamese.dyndns.org>
----- Original Message -----
From: Junio C Hamano
Date: 9/25/2010 12:06 AM
> Joshua Jensen<jjensen@workspacewhiz.com> writes:
>> I've come to accept the term 'needs update' when I've forgotten to
>> stash or commit before certain Git operations. However, I got
>> cornered today and was asked to explain what it means. I had to admit
>> I don't know.
> It came from "you need to run update-index on that path, as you have local
> modification in the working tree".
Okay, your description makes sense to me, and I'll be able to explain
what it means.
I did a Google search before I posted here. It turns out this phrase is
*very* confusing to others. Casual Joes don't use the plumbing commands
(which I assume git update-index is). Is there opposition to
modernizing this turn to make it more clear based on the porcelain
commands being run?
Thanks.
Josh
next prev parent reply other threads:[~2010-09-25 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 5:18 What exactly does 'needs update' mean? Joshua Jensen
2010-09-25 6:06 ` Junio C Hamano
2010-09-25 14:16 ` Joshua Jensen [this message]
2010-09-25 14:31 ` Joshua Jensen
2010-09-26 15:21 ` [PATCH 0/2] Eliminate cryptic "needs update" error message Ramkumar Ramachandra
2010-09-26 15:21 ` [PATCH 1/2] sh-setup: Write a new require_clean_work_tree function Ramkumar Ramachandra
2010-09-26 16:28 ` Matthieu Moy
2010-09-26 17:39 ` Ramkumar Ramachandra
2010-09-26 18:46 ` Matthieu Moy
2010-09-26 18:51 ` Ramkumar Ramachandra
2010-09-26 15:21 ` [PATCH 2/2] Porcelain scripts: Rewrite cryptic "needs update" error message Ramkumar Ramachandra
2010-09-26 16:31 ` Matthieu Moy
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=4C9E0427.9080901@workspacewhiz.com \
--to=jjensen@workspacewhiz.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).