From: Dan Nicolaescu <dann@ics.uci.edu>
To: Miles Bader <miles@gnu.org>
Cc: 2676@emacsbugs.donarmstrong.com
Subject: bug#2676: 23.0.91; annoying/unnecessary vc-next-action conflict in vc-dir buffer
Date: Mon, 16 Mar 2009 18:00:14 -0700 (PDT) [thread overview]
Message-ID: <200903170100.n2H10Ec4011190@godzilla.ics.uci.edu> (raw)
In-Reply-To: <fc339e4a0903151730kaf33539m7b4802a57face526@mail.gmail.com> (Miles Bader's message of "Mon, 16 Mar 2009 09:30:36 +0900")
Miles Bader <miles@gnu.org> writes:
> On Sun, Mar 15, 2009 at 11:53 PM, Dan Nicolaescu <dann@ics.uci.edu> wrote:
> > Not sure if such behavior is desirable. It's not unusual to have log
> > files, debug output, and various other files that don't satisfy a
> > pattern in the current directory. Registering such file and checking
> > them in by mistake does not seem such a good idea.
>
> Hmm, you're right, that might cause problems.
In that case you can close this bug, right?
> 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!
next prev parent reply other threads:[~2009-03-17 1:00 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 [this message]
2009-03-17 1:10 ` Miles Bader
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
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=200903170100.n2H10Ec4011190@godzilla.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=2676@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).