* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
@ 2015-10-11 22:35 Paul Eggert
2015-10-12 11:14 ` Michael Albinus
0 siblings, 1 reply; 14+ messages in thread
From: Paul Eggert @ 2015-10-11 22:35 UTC (permalink / raw)
To: 21669
[-- Attachment #1: Type: text/plain, Size: 368 bytes --]
This is to some extent a followup to Bug#21668, as it reports a similar kind of
test failure.
The file-notify-tests test fails for me routinely. Not always, though; it's not
reproducible in general. Attached is a sample log. I don't want to spend time
debugging this myself, but thought that whoever wants to know about this test
failure should know about it.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: file-notify-tests.log --]
[-- Type: text/x-log; name="file-notify-tests.log", Size: 2001 bytes --]
Running 12 tests (2015-10-11 15:27:10-0700)
Local library: `inotify'
passed 1/12 file-notify-test00-availability
Remote command: `gvfs-monitor-dir'
passed 2/12 file-notify-test00-availability-remote
passed 3/12 file-notify-test01-add-watch
passed 4/12 file-notify-test01-add-watch-remote
passed 5/12 file-notify-test02-events
Test file-notify-test02-events-remote backtrace:
#[0 "\306\307\310C\307C\3111(\0\312\313\314\315\316\x06\b\x06\b\x06\b\x06\b$\317\"\32
#[0 "\b\x19\303\304!\305\306\307C\306C\3101-\0\311\312\313\314\315\x06\b\x06\b\x06\b\x06
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test file-notify-test02-events-remote "C
ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test f
ert-run-tests(t #[385 "\306\x02\307\"\203G\0\211\211G\310U\203\x14\0\211@\20
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
command-line-1(("-L" ":." "-l" "ert" "-l" "file-notify-tests.elc" "-
command-line()
normal-top-level()
Test file-notify-test02-events-remote condition:
(ert-test-failed
((should
(equal '...
(mapcar ... file-notify--test-events)))
:form
(equal
(attribute-changed attribute-changed)
nil)
:value nil :explanation
(different-types
(attribute-changed attribute-changed)
nil)))
FAILED 6/12 file-notify-test02-events-remote
Reverting buffer `file-notify-test21588I8I'.
passed 7/12 file-notify-test03-autorevert
Reverting buffer `file-notify-test21588VGP'.
passed 8/12 file-notify-test03-autorevert-remote
passed 9/12 file-notify-test04-file-validity
passed 10/12 file-notify-test04-file-validity-remote
passed 11/12 file-notify-test05-dir-validity
passed 12/12 file-notify-test05-dir-validity-remote
Ran 12 tests, 11 results as expected, 1 unexpected (2015-10-11 15:27:58-0700)
1 unexpected results:
FAILED file-notify-test02-events-remote
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-11 22:35 bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64 Paul Eggert
@ 2015-10-12 11:14 ` Michael Albinus
2015-10-13 1:36 ` Paul Eggert
0 siblings, 1 reply; 14+ messages in thread
From: Michael Albinus @ 2015-10-12 11:14 UTC (permalink / raw)
To: Paul Eggert; +Cc: 21669
Paul Eggert <eggert@cs.ucla.edu> writes:
> This is to some extent a followup to Bug#21668, as it reports a
> similar kind of test failure.
>
> The file-notify-tests test fails for me routinely. Not always,
> though; it's not reproducible in general. Attached is a sample log.
> I don't want to spend time debugging this myself, but thought that
> whoever wants to know about this test failure should know about it.
Same here; I'll check when possible. This error is related to a Tramp
test case. As silly counter-measure, could you modify
`file-notify--test-timeout' in order to have a larger timeout than 6
seconds?
Best regards, Michael.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-12 11:14 ` Michael Albinus
@ 2015-10-13 1:36 ` Paul Eggert
2015-10-13 7:46 ` Michael Albinus
0 siblings, 1 reply; 14+ messages in thread
From: Paul Eggert @ 2015-10-13 1:36 UTC (permalink / raw)
To: Michael Albinus; +Cc: 21669
Michael Albinus wrote:
> As silly counter-measure, could you modify
> `file-notify--test-timeout' in order to have a larger timeout than 6
> seconds?
Is that something you could do for me, by changing it in master? To be honest I
don't want to spend a lot of time worrying about this one....
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-13 1:36 ` Paul Eggert
@ 2015-10-13 7:46 ` Michael Albinus
2015-10-16 20:20 ` Paul Eggert
0 siblings, 1 reply; 14+ messages in thread
From: Michael Albinus @ 2015-10-13 7:46 UTC (permalink / raw)
To: Paul Eggert; +Cc: 21669
Paul Eggert <eggert@cs.ucla.edu> writes:
>> As silly counter-measure, could you modify
>> `file-notify--test-timeout' in order to have a larger timeout than 6
>> seconds?
>
> Is that something you could do for me, by changing it in master? To
> be honest I don't want to spend a lot of time worrying about this
> one....
Done. Pls let us know, whether it solves the problem for you.
Best regards, Michael.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-13 7:46 ` Michael Albinus
@ 2015-10-16 20:20 ` Paul Eggert
2015-10-17 9:27 ` Michael Albinus
0 siblings, 1 reply; 14+ messages in thread
From: Paul Eggert @ 2015-10-16 20:20 UTC (permalink / raw)
To: Michael Albinus; +Cc: 21669
[-- Attachment #1: Type: text/plain, Size: 572 bytes --]
On 10/13/2015 12:46 AM, Michael Albinus wrote:
>> Is that something you could do for me, by changing it in master? To
>> >be honest I don't want to spend a lot of time worrying about this
>> >one....
> Done. Pls let us know, whether it solves the problem for you.
>
> Best regards, Michael.
Unfortunately it does not. Most of the time file-notify-tests succeeds,
but it occasionally fails. I'm attaching a failure log, generated from
commit 1e1a326c0f609f403c625bd9082e1099a4d9a52a and built with GCC 5.2
on Fedora 21 x86-64 with './configure --enable-gcc-warnings'.
[-- Attachment #2: file-notify-tests.log --]
[-- Type: text/plain, Size: 1949 bytes --]
Running 12 tests (2015-10-16 13:14:40-0700)
Local library: `inotify'
passed 1/12 file-notify-test00-availability
Remote command: `gvfs-monitor-dir'
passed 2/12 file-notify-test00-availability-remote
passed 3/12 file-notify-test01-add-watch
passed 4/12 file-notify-test01-add-watch-remote
passed 5/12 file-notify-test02-events
Test file-notify-test02-events-remote backtrace:
#[0 "\306\307\310C\307C\3111(\0\312\313\314\315\316\x06\b\x06\b\x06\b\x06\b$\317\"\32
#[0 "\b\x19\303\304!\305\306\307C\306C\3101-\0\311\312\313\314\315\x06\b\x06\b\x06\b\x06
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test file-notify-test02-events-remote "C
ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test f
ert-run-tests(t #[385 "\306\x02\307\"\203G\0\211\211G\310U\203\x14\0\211@\20
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
command-line-1(("-L" ":." "-l" "ert" "-l" "file-notify-tests.elc" "-
command-line()
normal-top-level()
Test file-notify-test02-events-remote condition:
(ert-test-failed
((should
(equal '...
(mapcar ... file-notify--test-events)))
:form
(equal
(attribute-changed attribute-changed)
nil)
:value nil :explanation
(different-types
(attribute-changed attribute-changed)
nil)))
FAILED 6/12 file-notify-test02-events-remote
Reverting buffer `file-notify-test24487EdC'.
passed 7/12 file-notify-test03-autorevert
Reverting buffer `file-notify-test24487RnI'.
passed 8/12 file-notify-test03-autorevert-remote
passed 9/12 file-notify-test04-file-validity
passed 10/12 file-notify-test04-file-validity-remote
passed 11/12 file-notify-test05-dir-validity
passed 12/12 file-notify-test05-dir-validity-remote
Ran 12 tests, 11 results as expected, 1 unexpected (2015-10-16 13:15:30-0700)
1 unexpected results:
FAILED file-notify-test02-events-remote
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-16 20:20 ` Paul Eggert
@ 2015-10-17 9:27 ` Michael Albinus
2015-10-21 1:34 ` Paul Eggert
0 siblings, 1 reply; 14+ messages in thread
From: Michael Albinus @ 2015-10-17 9:27 UTC (permalink / raw)
To: Paul Eggert; +Cc: 21669
Paul Eggert <eggert@cs.ucla.edu> writes:
> Unfortunately it does not. Most of the time file-notify-tests
> succeeds, but it occasionally fails. I'm attaching a failure log,
> generated from commit 1e1a326c0f609f403c625bd9082e1099a4d9a52a and
> built with GCC 5.2 on Fedora 21 x86-64 with './configure
> --enable-gcc-warnings'.
>
> Running 12 tests (2015-10-16 13:14:40-0700)
> Local library: `inotify'
> passed 1/12 file-notify-test00-availability
> Remote command: `gvfs-monitor-dir'
>
> 1 unexpected results:
> FAILED file-notify-test02-events-remote
Well, with gfilenotify it is known that there are timimg issues if
events occur in short period. Some of them are suppressed then, likely
as performance feature of gio.
With the local gfilenotify library (not used in your case) I could fix
this; the remote gvfs-monitor-dir process does not offer an argument for
changing the timing.
I've changed file-notify-tests.el in order to handle this. Could you,
pls, check?
Best regards, Michael.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-17 9:27 ` Michael Albinus
@ 2015-10-21 1:34 ` Paul Eggert
2015-10-21 8:01 ` Michael Albinus
0 siblings, 1 reply; 14+ messages in thread
From: Paul Eggert @ 2015-10-21 1:34 UTC (permalink / raw)
To: Michael Albinus; +Cc: 21669
[-- Attachment #1: Type: text/plain, Size: 214 bytes --]
Michael Albinus wrote:
> I've changed file-notify-tests.el in order to handle this. Could you,
> pls, check?
Still not working, I'm afraid. Failures are intermittent. A failing
file-notify-tests.log is attached.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: file-notify-tests.log --]
[-- Type: text/x-log; name="file-notify-tests.log", Size: 2074 bytes --]
Running 12 tests (2015-10-20 18:31:13-0700)
Local library: `inotify'
passed 1/12 file-notify-test00-availability
Remote command: `gvfs-monitor-dir'
passed 2/12 file-notify-test00-availability-remote
passed 3/12 file-notify-test01-add-watch
passed 4/12 file-notify-test01-add-watch-remote
passed 5/12 file-notify-test02-events
Test file-notify-test02-events-remote backtrace:
#[0 "\306\307\310C\307C\3111(\0\312\313\314\315\316\x06\b\x06\b\x06\b\x06\b$\317\"\32
#[0 "\b\x19\303\304!\305\306\307C\306C\3101-\0\311\312\313\314\315\x06\b\x06\b\x06\b\x06
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test file-notify-test02-events-remote "C
ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test f
ert-run-tests(t #[385 "\306\x02\307\"\203G\0\211\211G\310U\203\x14\0\211@\20
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
command-line-1(("-L" ":." "-l" "ert" "-l" "file-notify-tests.elc" "-
command-line()
normal-top-level()
Test file-notify-test02-events-remote condition:
(ert-test-failed
((should
(equal '...
(mapcar ... file-notify--test-events)))
:form
(equal
(attribute-changed)
(attribute-changed attribute-changed))
:value nil :explanation
(proper-lists-of-different-length 1 2
(attribute-changed)
(attribute-changed attribute-changed)
first-mismatch-at 1)))
FAILED 6/12 file-notify-test02-events-remote
Reverting buffer `file-notify-test1422adk'.
passed 7/12 file-notify-test03-autorevert
Reverting buffer `file-notify-test1422nnq'.
passed 8/12 file-notify-test03-autorevert-remote
passed 9/12 file-notify-test04-file-validity
passed 10/12 file-notify-test04-file-validity-remote
passed 11/12 file-notify-test05-dir-validity
passed 12/12 file-notify-test05-dir-validity-remote
Ran 12 tests, 11 results as expected, 1 unexpected (2015-10-20 18:32:01-0700)
1 unexpected results:
FAILED file-notify-test02-events-remote
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-21 1:34 ` Paul Eggert
@ 2015-10-21 8:01 ` Michael Albinus
2015-10-21 16:03 ` Paul Eggert
0 siblings, 1 reply; 14+ messages in thread
From: Michael Albinus @ 2015-10-21 8:01 UTC (permalink / raw)
To: Paul Eggert; +Cc: 21669
Paul Eggert <eggert@cs.ucla.edu> writes:
Hi Paul,
>> I've changed file-notify-tests.el in order to handle this. Could you,
>> pls, check?
>
> Still not working, I'm afraid. Failures are intermittent. A failing
> file-notify-tests.log is attached.
Are you sure you've got the recent 57be62f97b8442218f4fa6979cf27b36d5d5f540
of test/automated/file-notify-tests.el, and it is also compiled? The
test for
> (proper-lists-of-different-length 1 2
> (attribute-changed)
> (attribute-changed attribute-changed)
> first-mismatch-at 1)))
is NOT part any longer of this file.
Best regards, Michael.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-21 8:01 ` Michael Albinus
@ 2015-10-21 16:03 ` Paul Eggert
2015-10-21 18:25 ` Michael Albinus
2015-10-23 11:31 ` Michael Albinus
0 siblings, 2 replies; 14+ messages in thread
From: Paul Eggert @ 2015-10-21 16:03 UTC (permalink / raw)
To: Michael Albinus; +Cc: 21669
[-- Attachment #1: Type: text/plain, Size: 960 bytes --]
On 10/21/2015 01:01 AM, Michael Albinus wrote:
> Are you sure you've got the recent 57be62f97b8442218f4fa6979cf27b36d5d5f540
> of test/automated/file-notify-tests.el, and it is also compiled? The
> test for
>
>> > (proper-lists-of-different-length 1 2
>> > (attribute-changed)
>> > (attribute-changed attribute-changed)
>> > first-mismatch-at 1)))
> is NOT part any longer of this file.
I'm not sure for the failure I already sent you since I've git pulled
since then, but I just now reran the tests in master commit
f6ece2420c3dc6f3dde06c7f8722f5b0b7e1ef4a (which postdates the commit you
mention) and am still seeing intermittent failures. Failure log
attached. test/automated/file-notify-tests.el has been compiled:
$ ls -l test/automated/file-notify-tests.el*
-rw-r--r--. 1 eggert eggert 22497 Oct 20 18:16
test/automated/file-notify-tests.el
-rw-r--r--. 1 eggert eggert 37715 Oct 21 08:53
test/automated/file-notify-tests.elc
[-- Attachment #2: file-notify-tests.log --]
[-- Type: text/plain, Size: 2023 bytes --]
Running 12 tests (2015-10-21 08:54:15-0700)
Local library: `inotify'
passed 1/12 file-notify-test00-availability
Remote command: `gvfs-monitor-dir'
passed 2/12 file-notify-test00-availability-remote
passed 3/12 file-notify-test01-add-watch
passed 4/12 file-notify-test01-add-watch-remote
passed 5/12 file-notify-test02-events
Test file-notify-test02-events-remote backtrace:
#[0 "\306\307\310C\307C\3111(\0\312\313\314\315\316\x06\b\x06\b\x06\b\x06\b$\317\"\32
#[0 "\b\x19\303\304!\305\306\307C\306C\3101-\0\311\312\313\314\315\x06\b\x06\b\x06\b\x06
ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
ert-run-test([cl-struct-ert-test file-notify-test02-events-remote "C
ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test f
ert-run-tests(t #[385 "\306\x02\307\"\203G\0\211\211G\310U\203\x14\0\211@\20
ert-run-tests-batch(nil)
ert-run-tests-batch-and-exit()
command-line-1(("-L" ":." "-l" "ert" "-l" "file-notify-tests.elc" "-
command-line()
normal-top-level()
Test file-notify-test02-events-remote condition:
(ert-test-failed
((should
(equal '...
(mapcar ... file-notify--test-events)))
:form
(equal
(attribute-changed)
(attribute-changed attribute-changed))
:value nil :explanation
(proper-lists-of-different-length 1 2
(attribute-changed)
(attribute-changed attribute-changed)
first-mismatch-at 1)))
FAILED 6/12 file-notify-test02-events-remote
Reverting buffer `file-notify-test19070gGx'.
passed 7/12 file-notify-test03-autorevert
Reverting buffer `file-notify-test19070SQA'.
passed 8/12 file-notify-test03-autorevert-remote
passed 9/12 file-notify-test04-file-validity
passed 10/12 file-notify-test04-file-validity-remote
passed 11/12 file-notify-test05-dir-validity
passed 12/12 file-notify-test05-dir-validity-remote
Ran 12 tests, 11 results as expected, 1 unexpected (2015-10-21 08:55:04-0700)
1 unexpected results:
FAILED file-notify-test02-events-remote
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-21 16:03 ` Paul Eggert
@ 2015-10-21 18:25 ` Michael Albinus
2015-10-23 11:31 ` Michael Albinus
1 sibling, 0 replies; 14+ messages in thread
From: Michael Albinus @ 2015-10-21 18:25 UTC (permalink / raw)
To: Paul Eggert; +Cc: 21669
Paul Eggert <eggert@cs.ucla.edu> writes:
> I'm not sure for the failure I already sent you since I've git pulled
> since then, but I just now reran the tests in master commit
> f6ece2420c3dc6f3dde06c7f8722f5b0b7e1ef4a (which postdates the commit
> you mention) and am still seeing intermittent failures. Failure log
> attached. test/automated/file-notify-tests.el has been compiled:
Running many times the test, I could reproduce the error now once. I
will instrument the code, and see what happens. Hard to debug, likely a
timing issue.
Best regards, Michael.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-21 16:03 ` Paul Eggert
2015-10-21 18:25 ` Michael Albinus
@ 2015-10-23 11:31 ` Michael Albinus
2015-10-31 8:31 ` Michael Albinus
2015-10-31 12:49 ` Paul Eggert
1 sibling, 2 replies; 14+ messages in thread
From: Michael Albinus @ 2015-10-23 11:31 UTC (permalink / raw)
To: Paul Eggert; +Cc: 21669
Paul Eggert <eggert@cs.ucla.edu> writes:
Hi Paul,
> I'm not sure for the failure I already sent you since I've git pulled
> since then, but I just now reran the tests in master commit
> f6ece2420c3dc6f3dde06c7f8722f5b0b7e1ef4a (which postdates the commit
> you mention) and am still seeing intermittent failures.
Finally, I could fix it. Puhhh.
In fact, there were two problems:
- `write-region' fires in the local case just `created' and `changed'
events. In the remote case, it fires `created', `changed' and
`attribute-changed' events. This is because Tramp calls internally
`set-file-modes' on the newly created file.
- In the test case `file-notify-test02-events-remote' not all events did
arrive in time, because there was a fast sequence `write-region',
`set-file-modes', `delete-file'. So I had to introduce short
`sleep-for' calls between those functions.
I've committed a fix for both problems (and for one unrelated error in
filenotify.el I found also). I've run file-notify-tests.el 20 times now,
no error again. Could you, pls, recheck?
Best regards, Michael.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-23 11:31 ` Michael Albinus
@ 2015-10-31 8:31 ` Michael Albinus
2015-10-31 12:49 ` Paul Eggert
1 sibling, 0 replies; 14+ messages in thread
From: Michael Albinus @ 2015-10-31 8:31 UTC (permalink / raw)
To: Paul Eggert; +Cc: 21669
Michael Albinus <michael.albinus@gmx.de> writes:
> I've committed a fix for both problems (and for one unrelated error in
> filenotify.el I found also). I've run file-notify-tests.el 20 times now,
> no error again. Could you, pls, recheck?
Ping.
Best regards, Michael.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-23 11:31 ` Michael Albinus
2015-10-31 8:31 ` Michael Albinus
@ 2015-10-31 12:49 ` Paul Eggert
2015-10-31 13:36 ` Michael Albinus
1 sibling, 1 reply; 14+ messages in thread
From: Paul Eggert @ 2015-10-31 12:49 UTC (permalink / raw)
To: Michael Albinus; +Cc: 21669
Michael Albinus wrote:
> I've committed a fix for both problems (and for one unrelated error in
> filenotify.el I found also). I've run file-notify-tests.el 20 times now,
> no error again. Could you, pls, recheck?
It seems to be working for me too. Thanks.
^ permalink raw reply [flat|nested] 14+ messages in thread
* bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64
2015-10-31 12:49 ` Paul Eggert
@ 2015-10-31 13:36 ` Michael Albinus
0 siblings, 0 replies; 14+ messages in thread
From: Michael Albinus @ 2015-10-31 13:36 UTC (permalink / raw)
To: Paul Eggert; +Cc: 21669-done
Paul Eggert <eggert@cs.ucla.edu> writes:
> Michael Albinus wrote:
>> I've committed a fix for both problems (and for one unrelated error in
>> filenotify.el I found also). I've run file-notify-tests.el 20 times now,
>> no error again. Could you, pls, recheck?
>
> It seems to be working for me too. Thanks.
So I'm closing this bug, too. Thanks for testing.
Best regards, Michael.
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2015-10-31 13:36 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-10-11 22:35 bug#21669: 25.0.50; file-notify-tests failure on Fedora x86-64 Paul Eggert
2015-10-12 11:14 ` Michael Albinus
2015-10-13 1:36 ` Paul Eggert
2015-10-13 7:46 ` Michael Albinus
2015-10-16 20:20 ` Paul Eggert
2015-10-17 9:27 ` Michael Albinus
2015-10-21 1:34 ` Paul Eggert
2015-10-21 8:01 ` Michael Albinus
2015-10-21 16:03 ` Paul Eggert
2015-10-21 18:25 ` Michael Albinus
2015-10-23 11:31 ` Michael Albinus
2015-10-31 8:31 ` Michael Albinus
2015-10-31 12:49 ` Paul Eggert
2015-10-31 13:36 ` Michael Albinus
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).