all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: gnulib strftime imported into Emacs
Date: Tue, 1 Feb 2011 01:34:14 +0100	[thread overview]
Message-ID: <AANLkTikzkLucFMF+pyb=QuAQqSGqNG1rZjCngT495oBh@mail.gmail.com> (raw)
In-Reply-To: <4D4752A1.3020201@cs.ucla.edu>

On Tue, Feb 1, 2011 at 1:24 AM, Paul Eggert <eggert@cs.ucla.edu> wrote:
> On 01/31/11 16:15, Lennart Borgman wrote:
>> Perhaps it would be easier to publish the branch on Launchpad for
>> example? If you do that it is easy to automate the build so at least
>> the build process can be checked.
>
> Let's try doing it by patch-emailing first instead.  That's less work
> for me, and I expect just as reliable.  If it doesn't work we can try
> something else.

Ok.


>> There is currently a test subdirectory in the repository. Can't you
>> put tests there?
>
> Well, I'm no expert, but as I understand it, the existence of
> the tests subdirectory is controversial, it's not much used or
> maintained, and it's not distributed as part of Emacs.

It has not been used much but it is our goal to add tests to Emacs.
(However it looks like it will not be distributed by prebuilt Emacs.
Which I personally think is unfortunate.)

> Besides, adding tests to the test subdirectory wouldn't have affected the issues
> that started this thread.  The problem wasn't a bug in a built Emacs.
> The problem was that Emacs didn't build under Windows.  I expect that
> future issues in this area will be similar.

I see. I thought the built Emacs needed testing too.



  reply	other threads:[~2011-02-01  0:34 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30 23:43 gnulib strftime imported into Emacs Paul Eggert
2011-01-31  4:00 ` Eli Zaretskii
2011-01-31  8:02   ` Paul Eggert
2011-01-31  9:44     ` joakim
2011-01-31  9:59       ` Miles Bader
2011-01-31 10:16         ` joakim
2011-01-31 10:31           ` Miles Bader
2011-01-31 11:27       ` Eli Zaretskii
2011-01-31 11:06     ` Eli Zaretskii
2011-01-31 14:30       ` Tom Tromey
2011-01-31 14:43         ` Eli Zaretskii
2011-01-31 19:49           ` Eli Zaretskii
2011-01-31 22:19       ` Paul Eggert
2011-01-31 22:29         ` Lennart Borgman
2011-01-31 23:57           ` Paul Eggert
2011-02-01  0:15             ` Lennart Borgman
2011-02-01  0:24               ` Paul Eggert
2011-02-01  0:34                 ` Lennart Borgman [this message]
2011-02-01  4:05         ` Eli Zaretskii
2011-02-01  7:08           ` Paul Eggert
2011-02-01  8:58             ` Avoiding slowdown in trunk development (was: gnulib strftime imported into Emacs) Eli Zaretskii
2011-02-01 19:04               ` Avoiding slowdown in trunk development Paul Eggert
2011-02-01 19:54                 ` Lennart Borgman
2011-02-01 19:57                 ` Eli Zaretskii
2011-02-02 16:52                 ` Chong Yidong
2011-01-31 11:17     ` gnulib strftime imported into Emacs Lennart Borgman
2011-01-31 11:37       ` Eli Zaretskii
2011-01-31 11:52         ` Lennart Borgman
2011-01-31 13:01           ` Eli Zaretskii
2011-01-31 13:17             ` Andreas Schwab
2011-01-31 14:44               ` Eli Zaretskii
2011-01-31 14:54                 ` Andreas Schwab
2011-01-31 15:14                   ` Eli Zaretskii
2011-01-31 13:18             ` Lennart Borgman
2011-01-31 14:45             ` Eli Zaretskii
2011-01-31 19:50       ` Eli Zaretskii
2011-01-31 11:32     ` Andy Moreton
2011-01-31 19:53   ` Eli Zaretskii
2011-01-31 14:56 ` Eli Zaretskii
2011-01-31 16:56   ` Stefan Monnier
2011-01-31 20:06     ` Eli Zaretskii
2011-01-31 20:42       ` Stefan Monnier
2011-01-31 19:54 ` Eli Zaretskii
2011-01-31 23:25   ` Paul Eggert
2011-02-01  4:07     ` Eli Zaretskii
2011-02-01  6:25       ` Paul Eggert
2011-02-01  8:32         ` Eli Zaretskii

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='AANLkTikzkLucFMF+pyb=QuAQqSGqNG1rZjCngT495oBh@mail.gmail.com' \
    --to=lennart.borgman@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --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 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.