From: Miles Bader <miles@gnu.org>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 2676@emacsbugs.donarmstrong.com
Subject: bug#2676: 23.0.91; annoying/unnecessary vc-next-action conflict in vc-dir buffer
Date: Tue, 17 Mar 2009 10:10:18 +0900 [thread overview]
Message-ID: <fc339e4a0903161810i563c966bp528bf652df3cb95d@mail.gmail.com> (raw)
In-Reply-To: <200903170100.n2H10Ec4011190@godzilla.ics.uci.edu>
On Tue, Mar 17, 2009 at 10:00 AM, Dan Nicolaescu <dann@ics.uci.edu> wrote:
> > Hmm, you're right, that might cause problems.
>
> In that case you can close this bug, right?
Can I close bugs...?
> > Your advice about using "M" was useful, it would be cool if vc-dir
> > could give such advice... :-)
>
> [METALIC VOICE]: This is vc-dir speaking follow everything I say!
Seriously... if you've ever used git much, in some situations it
gives user-oriented advice like "if you want to do foo, you might want
to use comand x y z ...", and it's often a _really_ useful hint, even
if you've used git for a while (and the location of such advice is
tastefully chosen so that it's not annoying for experienced users).
One can figure out what the current vc-next-action conflict error
messages mean with a bit of thought, but they seem sort of
user-hostile, almost designed to cause one's eyes to glaze over...
-Miles
--
Do not taunt Happy Fun Ball.
next prev parent reply other threads:[~2009-03-17 1:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fc339e4a0903180443k2d2539di2df31c82628bad08@mail.gmail.com>
2009-03-15 2:57 ` bug#2676: 23.0.91; annoying/unnecessary vc-next-action conflict in vc-dir buffer Miles Bader
2009-03-15 14:53 ` Dan Nicolaescu
2009-03-16 0:30 ` Miles Bader
2009-03-17 1:00 ` Dan Nicolaescu
2009-03-17 1:10 ` Miles Bader [this message]
2009-03-17 2:07 ` Dan Nicolaescu
2009-03-18 11:50 ` bug#2676: marked as done (23.0.91; annoying/unnecessary vc-next-action conflict in vc-dir buffer) Emacs bug Tracking System
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=fc339e4a0903161810i563c966bp528bf652df3cb95d@mail.gmail.com \
--to=miles@gnu.org \
--cc=2676@emacsbugs.donarmstrong.com \
--cc=dann@ics.uci.edu \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.