From: Dan Nicolaescu <dann@ics.uci.edu>
To: Miles Bader <miles@gnu.org>
Cc: 2675@emacsbugs.donarmstrong.com
Subject: bug#2675: 23.0.91; unnecessary vc-next-action conflicts in vc-dir directory
Date: Mon, 16 Mar 2009 17:58:50 -0700 (PDT) [thread overview]
Message-ID: <200903170058.n2H0woN8011160@godzilla.ics.uci.edu> (raw)
In-Reply-To: <87tz5u9y92.fsf@catnip.gol.com> (Miles Bader's message of "Mon, 16 Mar 2009 08:12:25 +0900")
Miles Bader <miles@gnu.org> writes:
> Dan Nicolaescu <dann@ics.uci.edu> writes:
> > Personally, I disagree with that.
> > Anyway, vc-dir is the wrong tree to bark at, you want to have
> > vc-next-action + vc-compatible-state changed and this issue will
> > disappear.
>
> FWIW, I just did `report-emacs-bug', I didn't intend to register this as
> a vc-dir bug in particular (or anything else, though vc-next-action is
> the command invoked). Is there a protocol for filing bugs against
> specific parts of emacs?
No idea. Somehow vc-dir managed to get itself a bug category (not very
useful given that it's so small, a vc category would be more useful,
but...).
But the interesting thing is that I don't remember at the moment any bug
in that category that is/was a vc-dir bug, most were vc bugs, or various
vc-backend bugs.
next prev parent reply other threads:[~2009-03-17 0:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 2:46 bug#2675: 23.0.91; unnecessary vc-next-action conflicts in vc-dir directory Miles Bader
2009-03-15 9:20 ` Dan Nicolaescu
2009-03-15 10:01 ` Miles Bader
2009-03-15 15:07 ` Dan Nicolaescu
[not found] ` <mailman.3233.1237130630.31690.bug-gnu-emacs@gnu.org>
2009-03-15 23:12 ` Miles Bader
2009-03-17 0:58 ` Dan Nicolaescu [this message]
2009-03-16 0:50 ` Stefan Monnier
2009-03-16 1:12 ` Miles Bader
2009-03-17 1:08 ` Dan Nicolaescu
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200903170058.n2H0woN8011160@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=2675@emacsbugs.donarmstrong.com \
--cc=miles@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).