From: Jakub Narebski <jnareb@gmail.com>
To: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: git@vger.kernel.org
Subject: Re: git UI nit
Date: Wed, 6 Dec 2006 17:23:23 +0100 [thread overview]
Message-ID: <200612061723.23515.jnareb@gmail.com> (raw)
In-Reply-To: <4576EA02.2010809@xs4all.nl>
Han-Wen Nienhuys wrote:
> Jakub Narebski escreveu:
>> Johannes Schindelin wrote:
>>
>>> On Wed, 6 Dec 2006, Han-Wen Nienhuys wrote:
>>>
>>>> Johannes Schindelin escreveu:
>>>>> }
>>>>> if (quiet)
>>>>> continue;
>>>>> - printf("%s: needs update\n", ce->name);
>>>>> + printf("%s: dirty; needs commit\n", ce->name);
>>>> Yes - I'd just mention revert as an option too.
>>> Actually, I like it that short.
>>
>> So why not simply use "%s: dirty\n"?
>
> because a newbie doesn't know how to resolve that problem.
But there are [at least] two ways to resolve this:
commit or revert (reset).
--
Jakub Narebski
next prev parent reply other threads:[~2006-12-06 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 14:22 git UI nit Han-Wen Nienhuys
2006-12-06 14:46 ` Johannes Schindelin
2006-12-06 15:09 ` Han-Wen Nienhuys
2006-12-06 15:20 ` Johannes Schindelin
2006-12-06 15:36 ` Jakub Narebski
2006-12-06 16:04 ` Han-Wen Nienhuys
2006-12-06 16:23 ` Jakub Narebski [this message]
2006-12-06 15:41 ` Han-Wen Nienhuys
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=200612061723.23515.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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.