unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Glenn Morris <rgm@gnu.org>
Cc: 11632@debbugs.gnu.org
Subject: bug#11632: 24.1.50; Unrecognized bug debbugs:11140. Commit refused
Date: Tue, 05 Jun 2012 18:45:27 -0400	[thread overview]
Message-ID: <jwv8vg1mlbw.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <ec1ultr7ef.fsf@fencepost.gnu.org> (Glenn Morris's message of "Tue, 05 Jun 2012 13:32:56 -0400")

> PPS Should I file a bzr wishlist for them to add builtin support for this?
>> From `bzr help bugs':

>   These are the bugtrackers that are built in:
  
>     ============================ ============ ============
>     URL                          Abbreviation Example
>     ============================ ============ ============
>     https://bugs.launchpad.net/  lp           lp:12345
>     http://bugs.debian.org/      deb          deb:12345
>     http://bugzilla.gnome.org/   gnome        gnome:12345
>     ============================ ============ ============

> These are all much larger than bugs.gnu.org, so it seems a bit
> presumptuous to ask them to add it. I suppose the abbreviation would
> have to be "gnu".

They should just add

  bugtracker_http_url = http:{id}

so you can do "--fixes http://foo/bar" without any need to setup
specific bug trackers.  After, the expansion happens at commit time, so
there's no benefit to using a two-step process (e.g. if the bugtracker
location changes, you can't fix your bzr log anyway).


        Stefan





  reply	other threads:[~2012-06-05 22:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 16:40 bug#11632: 24.1.50; Unrecognized bug debbugs:11140. Commit refused Sam Steingold
2012-06-05 17:21 ` Glenn Morris
2012-06-05 17:24   ` Glenn Morris
2012-06-05 17:32     ` Glenn Morris
2012-06-05 22:45       ` Stefan Monnier [this message]
2012-06-05 22:46       ` Juanma Barranquero

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=jwv8vg1mlbw.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=11632@debbugs.gnu.org \
    --cc=rgm@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).