all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Fabrice Niessen <fni@missioncriticalit.com>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: [emacs-leuven-theme] diff-index foreground (#2bis)
Date: Sat, 28 Sep 2013 23:17:31 +0300	[thread overview]
Message-ID: <5247395B.1030602@yandex.ru> (raw)
In-Reply-To: <86mwmytknx.fsf@somewhere.org>

On 27.09.2013 17:16, Fabrice Niessen wrote:
> While thinking at it, even if there are still improvements which can be made
> (and which I will try to do) to leuven-theme.el, could you commit the current
> version into Emacs trunk?  Thanks a lot!

Sure, no problem, but please keep emacs-devel in Cc, since this kind of 
discussion belongs there.

Could you explain the following additions:

- "Version:" header, apparently carrying the date of the commit.
- time-stamp-* local variables at the bottom of the file.

Melpa does not use the version header (just sets the version to the time 
of the last commit), and the time-stamp vars just seem useless to me.

Shall I remove both of these additions before checking in the new version?



       reply	other threads:[~2013-09-28 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fniessen/emacs-leuven-theme/issues/2@github.com>
     [not found] ` <fniessen/emacs-leuven-theme/issues/2/22233879@github.com>
     [not found]   ` <86ioy9n78u.fsf_-_@somewhere.org>
     [not found]     ` <864n96uzcq.fsf@somewhere.org>
     [not found]       ` <86mwmytknx.fsf@somewhere.org>
2013-09-28 20:17         ` Dmitry Gutov [this message]
     [not found]           ` <5247395B.1030602-o+MxOtu4lMCHXe+LvDLADg@public.gmane.org>
2013-10-01 19:56             ` [emacs-leuven-theme] diff-index foreground (#2bis) Fabrice Niessen
2013-10-02  3:05               ` Dmitry Gutov
     [not found]                 ` <524B8D69.2000100-o+MxOtu4lMCHXe+LvDLADg@public.gmane.org>
2013-10-02  5:06                   ` Fabrice Niessen
2013-10-03  3:41                 ` Stefan Monnier

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=5247395B.1030602@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=fni@missioncriticalit.com \
    /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.