all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Glenn Hutchings <zondo42@gmail.com>
Cc: 22032@debbugs.gnu.org
Subject: bug#22032: 24.3; VC doesn't handle hg hidden revisions
Date: Mon, 14 Dec 2015 05:30:57 +0200	[thread overview]
Message-ID: <566E37F1.4080107@yandex.ru> (raw)
In-Reply-To: <566D4E6D.2060804@gmail.com>

On 12/13/2015 12:54 PM, Glenn Hutchings wrote:
> if a repository has any
> changesets that are marked 'obsolete', and any mercurial command is
> issued by a user who hasn't enabled the extension, a warning message is
> printed to stderr:
>
>     obsolete feature not enabled but <N> markers found!

That's a pretty unhelpful message. Does it also happen if you remove the 
"--hidden" flag from the proposed definition?

Actually, do we even need the "not hidden()" check in the spec, if the 
command is called without "--hidden"?

> Looking at mercurial sources, there's no way to suppress this warning.
> I guess one workaround would be to have vc-hg-command skip over it if
> it's there.

I think we'd rather avoid applying the patch until the extension becomes 
standard.





  reply	other threads:[~2015-12-14  3:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 11:36 bug#22032: 24.3; VC doesn't handle hg hidden revisions Glenn Hutchings
2015-11-28  2:44 ` Dmitry Gutov
     [not found]   ` <5659C34E.4070300@gmail.com>
2015-11-28 18:09     ` Dmitry Gutov
2015-12-13 10:54       ` Glenn Hutchings
2015-12-14  3:30         ` Dmitry Gutov [this message]
     [not found]           ` <CA+hLqocwRQqXHZj1i8YOQiJS2c1nL7ahVP7OrdS=oizy=ct1XQ@mail.gmail.com>
2015-12-15 14:08             ` Dmitry Gutov
2015-12-15 23:53       ` Andy Moreton
2015-12-16  0:03         ` Dmitry Gutov
2015-12-16  3:02           ` Andy Moreton
2015-12-18  5:02             ` Dmitry Gutov
2015-12-22 20:17               ` Glenn Hutchings
2015-12-22 21:33                 ` Dmitry Gutov

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=566E37F1.4080107@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=22032@debbugs.gnu.org \
    --cc=zondo42@gmail.com \
    /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.