all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: sds@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: grep breakage
Date: Wed, 09 Feb 2011 22:54:03 +0200	[thread overview]
Message-ID: <83d3n1rkt0.fsf@gnu.org> (raw)
In-Reply-To: <svfwrxhun7.fsf@tbox.m2.algo>

> From: Sam Steingold <sds@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Wed, 09 Feb 2011 14:31:40 -0500
> 
> > * Eli Zaretskii <ryvm@tah.bet> [2011-02-09 21:24:45 +0200]:
> >> 
> >> > * Chong Yidong <plq@fghcvqpuvpxra.pbz> [2011-02-09 11:04:51 -0500]:
> >> >
> >> >> I thought that the bug tracker was for the released versions.
> >> >
> >> > Nope, the same rationale applies to using the bug tracker for the
> >> > development and released versions.
> >> 
> >> should I report the global.h windows issue of this morning to the bug
> >> tracker?
> >
> > No, it doesn't make sense to use the bug tracker for such transient
> > problems.
> 
> Now I am _eminently_ confused.
>  :-(

How can I help you with that confusion?

We simply don't use to report build breakages to the bug tracker.  All
the other bugs should be reported there.



      reply	other threads:[~2011-02-09 20:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 15:03 rgrep breakage Sam Steingold
2011-02-08 23:58 ` grep breakage Sam Steingold
2011-02-09  0:02   ` Glenn Morris
2011-02-09 15:30     ` Sam Steingold
2011-02-09 16:04       ` Chong Yidong
2011-02-09 16:28         ` Sam Steingold
2011-02-09 18:38           ` Glenn Morris
2011-02-09 19:24           ` Eli Zaretskii
2011-02-09 19:31             ` Sam Steingold
2011-02-09 20:54               ` Eli Zaretskii [this message]

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=83d3n1rkt0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sds@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 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.