emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Bastien <bzg@gnu.org>
Cc: emacs-devel@gnu.org, emacs-orgmode@gnu.org,
	Lele Gaifax <lele@metapensiero.it>
Subject: Re: org-export raises stringp nil error
Date: Fri, 08 Mar 2013 17:20:40 +0900	[thread overview]
Message-ID: <8738w6i9pj.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <87vc928kcm.fsf@bzg.ath.cx>

Bastien writes:

 > I find it hard to draw a clear line between regressions and bugs,
 > especially since Org 7.9.x versions are way behind the current Org
 > master branch.

A regression is a feature that is missing, incomplete, or buggy in the
current HEAD that was present, complete, and correct in some ancestor
of HEAD that preceded the feature freeze.  If it's difficult to
identify regressions by that definition, you probably should not even
try to work on the Emacs prerelease branch except by request of the
release engineer.

Some release engineers (not me ;-) may restrict "ancestor" to be the
previous released version.  All release engineers I know restrict HEAD
and ancestor to versions of the project they manage. ;-)

      parent reply	other threads:[~2013-03-08  8:20 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87ip539io1.fsf@nautilus.nautilus>
2013-03-07 21:14 ` org-export raises stringp nil error Glenn Morris
2013-03-07 22:38   ` Bastien
2013-03-08  1:36     ` Glenn Morris
2013-03-08  6:40       ` Bastien
2013-03-08  7:16         ` Leo Liu
2013-03-08  7:37           ` Bastien
2013-03-08  7:44             ` Leo Liu
2013-03-08  7:56             ` Xue Fuqiao
2013-03-08  8:28           ` Eli Zaretskii
2013-03-08  9:15             ` joakim
2013-03-08  9:17               ` Bastien
2013-03-08  9:19               ` Bastien
2013-03-08  9:25               ` Dmitry Gutov
2013-03-08 10:23                 ` Eli Zaretskii
2013-03-08 11:18                   ` Dmitry Gutov
2013-03-08 14:06                     ` Eli Zaretskii
2013-03-08 21:00                       ` Dmitry Gutov
2013-03-08 16:34                   ` Achim Gratz
2013-03-08 19:48                     ` Eli Zaretskii
2013-03-08  9:55               ` Stephen J. Turnbull
2013-03-08 10:15               ` Eli Zaretskii
2013-03-08 11:12                 ` Dmitry Gutov
2013-03-08 14:21               ` Xue Fuqiao
2013-03-08 15:42                 ` Bastien
2013-03-08 16:29                   ` Nick Dokos
2013-03-08 16:38                     ` Jambunathan K
2013-03-08 17:09                       ` Bastien
2013-03-08 17:41                         ` Nick Dokos
2013-03-08 18:01                           ` Jambunathan K
2013-03-08 18:05                             ` Nick Dokos
2013-03-08 19:40                           ` Achim Gratz
2013-03-08 16:39                     ` Bastien
2013-03-08 22:37                     ` Xue Fuqiao
2013-03-08  7:47         ` Xue Fuqiao
2013-03-08  7:53           ` Bastien
2013-03-08  8:27           ` Stephen J. Turnbull
2013-03-08  8:58             ` Eli Zaretskii
2013-03-08  9:56               ` Stephen J. Turnbull
2013-03-08  8:30           ` Eli Zaretskii
2013-03-08  9:12             ` Bastien
2013-03-08  8:20         ` Stephen J. Turnbull [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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8738w6i9pj.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=bzg@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=lele@metapensiero.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/org-mode.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).