view admin/notes/years @ 107591:86eec24bee2c

Retrospective commit from 2009-09-26. Continued working on initialization. Started working on paragraph direction initialization. bidi.c (bidi_paragraph_init): Don't set bidi_it->ch_len. Abort if called not at beginning of a new paragraph. (bidi_get_next_char_visually): Prepare and use a sentinel iterator state when first_elt flag is set. dispextern.h (struct bidi_it): New struct member first_elt. bidi.c (bidi_init_it): Initialize bidi_it->first_elt. (bidi_copy_it): Don't copy the first_elt flag. xdisp.c (reseat_1): Initialize bidi_it.first_elt. Move bidi scan start code from here... (next_element_from_buffer): ...to here. Use bidi_it.first_elt flag.
author Eli Zaretskii <eliz@gnu.org>
date Fri, 01 Jan 2010 05:57:17 -0500
parents 0138ae02cb0d
children
line wrap: on
line source

HOW TO MAINTAIN COPYRIGHT YEARS FOR GNU EMACS

Maintaining copyright years is now very simple: every time a new year
rolls around, add that year to every FSF (and AIST) copyright notice.

There's no need to worry about whether an individual file has changed
in a given year - it's sufficient that Emacs as a whole has changed.

For more detailed information on maintaining copyright, see the file
"copyright" in this directory.

The previous policy was more complex, but is now only of historical
interest (see versions of this file from before 2009).

The refcards in etc/refcards can print only the latest copyright year,
but should keep the full list in a comment in the source.


"Our lawyer says it is ok if we add, to each file that has been in Emacs
 since Emacs 21 came out in 2001, all the subsequent years[1].  We don't
 need to check whether *that file* was changed in those years.
 It's sufficient that *Emacs* was changed in those years (and it was!).
  
 For those files that have been added since then, we should add
 the year it was added to Emacs, and all subsequent years."
  
 --RMS, 2005-07-13

[1] Note that this includes 2001 - see
<http://lists.gnu.org/archive/html/emacs-pretest-bug/2006-12/msg00119.html>