From: Eli Zaretskii <eliz@gnu.org>
To: James Cloos <cloos@jhcloos.com>
Cc: emacs-devel@gnu.org
Subject: Re: Icon displayed wrong
Date: Sat, 19 May 2007 11:16:50 +0300 [thread overview]
Message-ID: <ur6pdgrd9.fsf@gnu.org> (raw)
In-Reply-To: <m3fy5tw8uw.fsf@lugabout.jhcloos.org> (message from James Cloos on Sat, 19 May 2007 03:49:36 -0400)
> From: James Cloos <cloos@jhcloos.com>
> Cc: emacs-devel@gnu.org
> Date: Sat, 19 May 2007 03:49:36 -0400
>
> Eli> Can you explain why?
>
> The images directory has both B/W and Colour versions of each icon. The
> Colour versions are all xpm (X pixmap) files, and the B/W are all pbm
> (Portable Bitmap) files. All except cancel.pbm which has (had, on
> trunk, now that Glenn updated it) the bitmap extension but is (was) a
> grayscale file using only colours 0 and 255.
>
> Converting it simply makes it match all of the other icons, and it
> obviously was intended to be a P4 pbm file when it was first commited;
> whoever saved it from Gimp just "typo"ed the SaveAs on that one file.
In other words, you are saying it should be converted for consistency.
Note that there are a couple of other *.pbm files in etc/images that
on the branch are not PBM files. For example, copy.pbm is a PPM
file. Are we sure they all are due to typo-style mistakes?
> If there is any chance of .990 getting simply renamed as 22.1
There's exactly 0% chance that this will happen, because some source
files need to be modified to change the version number, and the
ChangeLog files need to be marked with the release entry.
> then I
> agree with Glenn's decision not to also make then change on the release
> branch. But it should then get done there for 22.2.
I actually agree with Glenn's decision not to touch the release
branch; see my other mail in this thread where I report that the
converted image file behaves differently from the original PGM one.
It is these unintended consequences that we should consider when we
discuss changes for non-critical problems.
next prev parent reply other threads:[~2007-05-19 8:16 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 8:09 FOR-RELEASE Glenn Morris
2007-05-17 21:32 ` Icon displayed wrong Richard Stallman
2007-05-17 21:39 ` Glenn Morris
2007-05-18 23:09 ` Richard Stallman
2007-05-19 0:32 ` James Cloos
2007-05-19 5:07 ` Glenn Morris
2007-05-19 7:53 ` Eli Zaretskii
2007-05-19 10:02 ` Jason Rumney
2007-05-19 11:12 ` Eli Zaretskii
2007-05-19 20:56 ` Glenn Morris
2007-05-19 21:08 ` David Kastrup
2007-05-19 22:31 ` Richard Stallman
2007-05-19 23:13 ` Glenn Morris
2007-05-19 23:18 ` Jason Rumney
2007-05-20 17:05 ` Richard Stallman
2007-05-20 20:26 ` Glenn Morris
2007-05-21 10:33 ` Richard Stallman
2007-05-19 7:38 ` Eli Zaretskii
2007-05-19 7:49 ` James Cloos
2007-05-19 8:16 ` Eli Zaretskii [this message]
2007-05-19 9:10 ` James Cloos
2007-05-18 15:03 ` FOR-RELEASE Chong Yidong
2007-05-19 10:55 ` FOR-RELEASE Richard Stallman
2007-05-21 12:44 ` FOR-RELEASE Giorgos Keramidas
2007-05-22 8:30 ` FOR-RELEASE Richard Stallman
2007-05-22 12:32 ` FOR-RELEASE Giorgos Keramidas
2007-05-22 23:09 ` FOR-RELEASE Richard Stallman
2007-05-19 18:51 ` FOR-RELEASE Chong Yidong
2007-05-24 21:22 ` FOR-RELEASE Richard Stallman
2007-05-24 23:23 ` FOR-RELEASE Chong Yidong
2007-05-26 0:19 ` FOR-RELEASE Richard Stallman
2007-05-26 4:41 ` FOR-RELEASE Glenn Morris
2007-05-27 14:21 ` FOR-RELEASE Richard Stallman
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=ur6pdgrd9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cloos@jhcloos.com \
--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 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).