diff options
| author | Stefan Monnier | 2004-12-07 05:01:55 +0000 |
|---|---|---|
| committer | Stefan Monnier | 2004-12-07 05:01:55 +0000 |
| commit | d3a403e56c880a3a0992079ebe5f280a22d7dd68 (patch) | |
| tree | 67787f98491074677037886da3238ac8ee681396 /admin | |
| parent | 516eb29c738876d545c59d1c9b47a793ffd835cc (diff) | |
| download | emacs-d3a403e56c880a3a0992079ebe5f280a22d7dd68.tar.gz emacs-d3a403e56c880a3a0992079ebe5f280a22d7dd68.zip | |
*** empty log message ***
Diffstat (limited to 'admin')
| -rw-r--r-- | admin/FOR-RELEASE | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/admin/FOR-RELEASE b/admin/FOR-RELEASE index 73e6d50df14..ca0e16bdec9 100644 --- a/admin/FOR-RELEASE +++ b/admin/FOR-RELEASE | |||
| @@ -36,6 +36,32 @@ invalid pointer from string_free_list. | |||
| 36 | 36 | ||
| 37 | * BUGS | 37 | * BUGS |
| 38 | 38 | ||
| 39 | ** Ange-ftp should ignore irrelevant IPv6 errors: | ||
| 40 | |||
| 41 | Message-Id: <4121-Tue23Mar2004165249+0100-piet@cs.uu.nl> | ||
| 42 | From: "Piet van Oostrum" <piet@cs.uu.nl> | ||
| 43 | To: emacs-pretest-bug@gnu.org | ||
| 44 | Subject: Ange-ftp can't deal with IPV6/IPV4 fallback | ||
| 45 | |||
| 46 | Symptoms: | ||
| 47 | |||
| 48 | C-x C-f /ftp.nluug.nl:/ | ||
| 49 | |||
| 50 | The problem is that the DNS first gives an IPV6 address. However our | ||
| 51 | router doesn't do IPV6. Ftp then falls back to IPV4: | ||
| 52 | |||
| 53 | ftp> open ftp.nluug.nl | ||
| 54 | Trying 2001:610:1:80aa:192:87:102:36... | ||
| 55 | ftp: connect to address 2001:610:1:80aa:192:87:102:36: No route to host | ||
| 56 | Trying 192.87.102.36... | ||
| 57 | Connected to ftp.nluug.nl. | ||
| 58 | |||
| 59 | Ange-ftp chokes on the `No route to host' message and doesn't look any | ||
| 60 | further. | ||
| 61 | |||
| 62 | I think in the near future we will see more of this problem, so it might be | ||
| 63 | time to make anfe-ftp more intelligent. | ||
| 64 | |||
| 39 | ** Mailabbrev should quote addresses to correspond to RFC 822. | 65 | ** Mailabbrev should quote addresses to correspond to RFC 822. |
| 40 | See http://article.gmane.org/gmane.emacs.devel/27585 | 66 | See http://article.gmane.org/gmane.emacs.devel/27585 |
| 41 | 67 | ||