From: Yuri Khan <yuri.v.khan@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: Bastien <bzg@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: org-merger questions
Date: Thu, 22 Jun 2017 17:46:47 +0700 [thread overview]
Message-ID: <CAP_d_8VZy7Dq6yog5X9nQGzdSQ_M1V-jj2BhSJ72Qa+Si1EJnQ@mail.gmail.com> (raw)
In-Reply-To: <87injotisu.fsf@gmx.us>
On Thu, Jun 22, 2017 at 5:31 PM, Rasmus <rasmus@gmx.us> wrote:
> Note that http://thaiopensource.com/ns/locating-rules/1.0 isn’t
> accessible.
XML namespace URIs are not supposed to be accessible. They are used as
opaque identifiers, guaranteed to be unique because presumably people
won’t allocate XML namespaces in domains they don’t own, and will
ensure uniqueness within domains they do own.
next prev parent reply other threads:[~2017-06-22 10:46 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 15:09 org-merger questions Rasmus
2017-06-21 15:23 ` Kaushal Modi
2017-06-21 16:16 ` Bastien Guerry
2017-06-22 10:31 ` Rasmus
2017-06-22 10:46 ` Yuri Khan [this message]
2017-06-22 16:01 ` Kyle Meyer
2017-06-22 18:11 ` Kyle Meyer
2017-06-23 9:04 ` Rasmus
2017-06-23 14:19 ` Kyle Meyer
2017-06-23 8:47 ` Rasmus
2017-06-23 14:30 ` Kyle Meyer
2017-06-23 14:37 ` Rasmus
2017-06-25 16:10 ` Kaushal Modi
2017-06-29 8:54 ` Rasmus
2017-06-29 9:12 ` Bastien Guerry
2017-06-29 16:13 ` John Wiegley
2017-07-03 7:19 ` Bastien
2017-07-03 15:56 ` Emacs master now updated to Org 9.0.9 (Was: org-merger questions) Kaushal Modi
2017-07-04 7:54 ` Emacs master now updated to Org 9.0.9 Bastien Guerry
2017-07-13 0:36 ` numbchild
2017-10-02 9:25 ` org-merger questions Bastien Guerry
2017-10-02 9:41 ` Rasmus
2017-10-02 9:46 ` Rasmus
2017-10-02 16:05 ` Eli Zaretskii
2017-10-11 22:31 ` Org mode update missing in NEWS (Was: Re: org-merger questions) Kaushal Modi
2017-10-12 7:54 ` Eli Zaretskii
2017-10-15 10:37 ` Org mode update missing in NEWS Rasmus
2017-06-21 15:27 ` org-merger questions Kyle Meyer
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=CAP_d_8VZy7Dq6yog5X9nQGzdSQ_M1V-jj2BhSJ72Qa+Si1EJnQ@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=bzg@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rasmus@gmx.us \
/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).