From: don@donarmstrong.com (Emacs bug Tracking System)
To: Luca Capello <luca@pca.it>
Cc: Emacs Bugs <bug-gnu-emacs@gnu.org>
Subject: Processed: Re: Delivery Notification: Delivery has failed
Date: Thu, 19 Jun 2008 07:25:05 -0700 [thread overview]
Message-ID: <handler.s.C.121388498212948.transcript@emacsbugs.donarmstrong.com> (raw)
In-Reply-To: <871w2t1pef.fsf@gismo.pca.it>
Processing commands for control@emacsbugs.donarmstrong.com:
> reopen 431
bug#431: 23.0.60; `display-buffer' opens vertical instead of horizontal windows
bug reopened, originator not changed.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Don Armstrong
(administrator, Emacs bugs database)
parent reply other threads:[~2008-06-19 14:25 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <871w2t1pef.fsf@gismo.pca.it>]
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=handler.s.C.121388498212948.transcript@emacsbugs.donarmstrong.com \
--to=don@donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=luca@pca.it \
/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).