unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Thien-Thi Nguyen <ttn@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: copyright in .tex files
Date: 12 Aug 2005 21:25:50 -0400	[thread overview]
Message-ID: <jkiryaiq5d.fsf@glug.org> (raw)
In-Reply-To: <854q9xnap6.fsf@lola.goethe.zz>

David Kastrup <dak@gnu.org> writes:

> [\year usage unconventional but probably ok]

thanks for the explanation.

this winter i will dig into TeX (a bit) and perhaps
do some light future-proofing of the .tex files.
until then, looks like \def\year{2002, 2003, ...}
is most straightforward.

thi

      reply	other threads:[~2005-08-13  1:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-10 14:00 copyright in .tex files Thien-Thi Nguyen
2005-08-10 14:11 ` David Kastrup
2005-08-13  1:25   ` Thien-Thi Nguyen [this message]

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=jkiryaiq5d.fsf@glug.org \
    --to=ttn@gnu.org \
    --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).