unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: "andrés ramírez" <rrandresf@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, 29070@debbugs.gnu.org
Subject: bug#29070: 26.0.90; emacs-26.0.90 pretest
Date: Wed, 01 Nov 2017 19:47:15 -0400	[thread overview]
Message-ID: <87375xa7ek.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87mv46vmmq.fsf@gmail.com> ("andrés ramírez"'s message of "Tue,  31 Oct 2017 19:00:29 -0600")

andrés ramírez <rrandresf@gmail.com> writes:

> No problem. It compiled fine. And worked as expected.
>
> Thanks guys. 

In addition to Anreads' fix, I modified the error message for this case,
so we won't claim that the directory is a file for nil file-attributes.

For reference, the relevant commit are:

[1: 8453423c7c]: 2017-11-01 21:44:49 +0100
  Avoid wrong value from file-attributes on Linux kernel before 3.6
  https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=8453423c7c5e1886a301fb61c4077650f59e670b

[2: dc0a25c2f9]: 2017-11-01 19:39:34 -0400
  Give a more sensible message if file-attributes fails (Bug#29070)
  https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=dc0a25c2f9b44c697194bd0ec21c942125160544





  reply	other threads:[~2017-11-01 23:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 20:02 bug#29070: 26.0.90; emacs-26.0.90 pretest rrandresf
2017-10-30 20:14 ` Noam Postavsky
2017-10-30 21:25   ` rrandresf
2017-10-30 21:38     ` Noam Postavsky
2017-10-30 22:41       ` rrandresf
2017-10-30 23:07         ` Noam Postavsky
2017-10-30 23:36           ` andrés ramírez
2017-10-30 23:52             ` Noam Postavsky
2017-10-31  0:18               ` andrés ramírez
2017-10-31  0:41                 ` Noam Postavsky
2017-10-31  1:59                   ` andrés ramírez
2017-10-31  2:11                     ` Noam Postavsky
2017-10-31  2:32                       ` andrés ramírez
2017-10-31  2:49                         ` Noam Postavsky
2017-10-31  3:05                           ` andrés ramírez
2017-10-31  3:21                             ` Noam Postavsky
2017-10-31  3:27                               ` andrés ramírez
2017-10-31 10:30                                 ` Noam Postavsky
2017-10-31 12:12                                   ` andrés ramírez
2017-10-31 13:11                                     ` Andreas Schwab
2017-10-31 13:38                                       ` andrés ramírez
2017-10-31 14:27                                         ` Andreas Schwab
2017-10-31 15:18                                           ` andrés ramírez
2017-10-31 20:21                                             ` Andreas Schwab
2017-11-01  1:00                                               ` andrés ramírez
2017-11-01 23:47                                                 ` Noam Postavsky [this message]
2017-11-01 20:48                                             ` Andreas Schwab

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=87375xa7ek.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=29070@debbugs.gnu.org \
    --cc=rrandresf@gmail.com \
    --cc=schwab@linux-m68k.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 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).