From: Eli Zaretskii <eliz@gnu.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-devel@gnu.org
Subject: Re: org-export raises stringp nil error
Date: Sat, 09 Mar 2013 13:14:20 +0200 [thread overview]
Message-ID: <83boasygdv.fsf@gnu.org> (raw)
In-Reply-To: <87ppz8x249.fsf@Rainer.invalid>
> From: Achim Gratz <Stromeko@nexgo.de>
> Date: Sat, 09 Mar 2013 12:07:50 +0100
>
> If you made some directories subprojects (in Git parlance; bizarr
> probably also has something that is almost, but not entirely unlike it),
> your Emacs checkout would look exactly the same as today. What would
> change is that if you fixed a bug in e.g. Org, you would fix it in the
> Emacs branch of the Org repository and then commit the subproject within
> Emacs pointing to the new head that contains the fix.
That will work, but only if the same VCS is used by all the projects.
next prev parent reply other threads:[~2013-03-09 11:14 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-07 18:19 org-export raises stringp nil error Lele Gaifax
2013-03-07 21:14 ` 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 20:09 ` Achim Gratz
2013-03-09 9:01 ` Eli Zaretskii
2013-03-09 11:07 ` Achim Gratz
2013-03-09 11:14 ` Eli Zaretskii [this message]
2013-03-09 18:01 ` Stephen J. Turnbull
2013-03-09 17:53 ` Stephen J. Turnbull
2013-03-09 18:07 ` Eli Zaretskii
2013-03-10 12:41 ` Stephen J. Turnbull
2013-03-10 16:48 ` Eli Zaretskii
2013-03-11 1:19 ` Stephen J. Turnbull
2013-03-10 18:03 ` Bastien
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 ` [O] " 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
2013-03-07 22:48 ` Xue Fuqiao
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=83boasygdv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-devel@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).