unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: emacs-devel@gnu.org
Subject: Re: Patch: vc-hg -vs- vc-status
Date: Tue, 08 Jan 2008 18:45:48 -0700	[thread overview]
Message-ID: <m31w8rpy9f.fsf@fleche.redhat.com> (raw)
In-Reply-To: <200801090211.m092Bw9C024680@oogie-boogie.ics.uci.edu> (Dan Nicolaescu's message of "Tue\, 08 Jan 2008 18\:11\:52 -0800")

>>>>> "Dan" == Dan Nicolaescu <dann@ics.uci.edu> writes:

>> * vc-hg.el (vc-hg-dir-status): Don't pass -A to "hg status".

Dan> Duh, I was too quick to copy+paste, please check this in.

I don't have write access.

Tom

  reply	other threads:[~2008-01-09  1:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-09  0:48 Patch: vc-hg -vs- vc-status Tom Tromey
2008-01-09  2:11 ` Dan Nicolaescu
2008-01-09  1:45   ` Tom Tromey [this message]
2008-01-09  5:21     ` 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=m31w8rpy9f.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=dann@ics.uci.edu \
    --cc=emacs-devel@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).