From: Eli Zaretskii <eliz@gnu.org>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-devel@gnu.org
Subject: Re: Merging Org tests
Date: Tue, 14 Feb 2017 18:20:55 +0200 [thread overview]
Message-ID: <8337fg217c.fsf@gnu.org> (raw)
In-Reply-To: <871sv0oljt.fsf@gmx.us> (message from Rasmus on Tue, 14 Feb 2017 16:10:30 +0100)
> From: Rasmus <rasmus@gmx.us>
> Date: Tue, 14 Feb 2017 16:10:30 +0100
>
> I understand that it would be desirable to include the Org tests in Emacs.
Yes, I think so.
> The readme/file-organization file in the "test" dir of emacs.git is a bit
> confusing. Why does it talk about an "automated" folder that isn't there?
> I guess it's simply "lisp" folder.
Yes, that was a left-over from the old organization. I fixed the
text.
> Also, how strictly must the suggested file organization be followed?
> Skimming "make-test-deps.emacs-lisp" it seems it might have to be followed
> rather strictly. In Org, tests are already organized into a different
> file hierarchy and use a slightly different naming scheme.
Is it a problem to change Org test files to follow the current
organization below test/? IOW, put all the Org files in
test/lisp/org/?
> What would be the best strategy for including the Org tests in the Emacs
> repo?
>
> 1. Include Org tests in the "manual" folder and keep the current structure.
> 2. Start to reorganize the tests in the Org repo to follow the Emacs
> scheme.
> 3. Keep tests in the Org repo.
My preference is 2, if it's feasible.
Thanks.
next prev parent reply other threads:[~2017-02-14 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-14 15:10 Merging Org tests Rasmus
2017-02-14 16:20 ` Eli Zaretskii [this message]
2017-02-14 18:13 ` Phillip Lord
2017-02-14 19:16 ` Michael Albinus
2017-02-15 10:55 ` Phillip Lord
2017-02-15 11:32 ` Michael Albinus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8337fg217c.fsf@gnu.org \
--to=eliz@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.