From: Xue Fuqiao <xfq.free@gmail.com>
To: Leo <sdl.web@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: why bugs only fixed in trunk?
Date: Wed, 26 Dec 2012 14:45:25 +0800 [thread overview]
Message-ID: <20121226144525.cf36e9ee3b0b9ffb4f7618e0@gmail.com> (raw)
In-Reply-To: <m2ehidtxsu.fsf@gmail.com>
On Wed, 26 Dec 2012 09:19:29 +0800
Leo <sdl.web@gmail.com> wrote:
> One of the incentives to report bugs in the pretest is to have them
> squashed before the release. Unfortunately it seems most bugs are just
> fixed in trunk (which could mean wait another year for the fix) even if
> reported against a pretest build.
You can use the trunk branch.
> Anyway, I think I am discouraged to report bugs and inclined to just
> code a workaround in my .emacs.
I think that it's a stupid behavior.
And there are some bug fixes in other branches, for example:
http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-24&id=add2de3ef3911031d603315738f9c5de5533d9f4
http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=xwidget&id=b1aa5d2fdc95f5e5e26dd99c2b8ba92d11900b4e
http://git.savannah.gnu.org/cgit/emacs.git/commit/?h=concurrency&id=e795e6f23528caaa6d1b125057c584a0c998a7d6
--
Best regards, Xue Fuqiao.
http://www.emacswiki.org/emacs/XueFuqiao
next prev parent reply other threads:[~2012-12-26 6:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 1:19 why bugs only fixed in trunk? Leo
2012-12-26 1:44 ` Daniel Colascione
2012-12-26 12:43 ` Lars Ingebrigtsen
2012-12-26 16:34 ` Jay Belanger
2012-12-26 16:59 ` Bastien
2012-12-26 17:56 ` Daniel Colascione
2012-12-27 1:02 ` Leo
2012-12-27 3:48 ` Eli Zaretskii
2012-12-26 2:37 ` Chong Yidong
2012-12-26 4:50 ` Stephen J. Turnbull
2012-12-26 6:28 ` Jambunathan K
2012-12-26 7:00 ` Leo
2012-12-26 6:45 ` Xue Fuqiao [this message]
2012-12-26 10:59 ` Bastien
2012-12-26 12:04 ` Leo
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=20121226144525.cf36e9ee3b0b9ffb4f7618e0@gmail.com \
--to=xfq.free@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=sdl.web@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 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).