Commit b7235808 authored by Kenichi Handa's avatar Kenichi Handa
Browse files

Add bug number.

parents f0d13888 f53a6590
This file describes the CVS branch in which it is maintained.
This file describes the bzr branch in which it is maintained.
Everything below the line is branch-specific.
________________________________________________________________________
This is the trunk (sometimes mistakenly called "HEAD").
When people say "use CVS emacs", this is the branch they are talking
about. Likewise, a "cvs checkout" without the "-r" option results in
this branch.
When people say "use the development version of Emacs" or the
"bzr version of Emacs", this is the branch they are talking about.
Emacs development takes place on the trunk. Most of the time, Emacs
hackers add to it relatively free of constraint (aside from proper
......
HOW TO COMMIT CHANGES TO EMACS
http://lists.gnu.org/archive/html/emacs-devel/2009-03/msg00555.html
From: Miles Bader
Subject: commit style redux
Date: Tue, 31 Mar 2009 12:21:20 +0900
(1) Commit all changed files at once with a single log message (which
in CVS will result in an identical log message for all committed
files), not one-by-one. This is pretty easy using vc-dir now.
(2) Make the log message describe the entire changeset, perhaps
including relevant changelog entiries (I often don't bother with
the latter if it's a trivial sort of change).
Many modern source-control systems vaguely distinguish the first
line of the log message to use as a short summary for abbreviated
history listing (in arch this was explicitly called the summary,
but many other systems have a similar concept). So it's nice if
you can format the log entry like:
SHORTISH ONE-LINE SUMMARY
MULTIPLE-LINE DETAILED DESCRIPTION POSSIBLY INCLUDING (OR
CONSISTING OF) CHANGELOG ENTRIES
[Even with CVS this style is useful, because web CVS browsing
interfaces often include the first N words of the log message of
the most recent commit as a short "most recent change"
description.]
(3) Don't phrase log messages assuming the filename is known, because
in non-file-oriented systems (everything modern other than CVS),
the log listing tends to be treated as global information, and the
connection with specific files is less explicit.
For instance, currently I often see log messages like "Regenerate";
for modern source-control systems with a global log, it's better to
have something like "Regenerate configure".
Followup discussion:
http://lists.gnu.org/archive/html/emacs-devel/2010-01/msg00897.html
PREVIOUS GUIDELINES FOR CVS
For historical interest only, here is the old-style advice for CVS logs:
http://lists.gnu.org/archive/html/emacs-devel/2007-12/msg01208.html
From: Eli Zaretskii
Subject: Re: Log messages in CVS
Date: Sat, 29 Dec 2007 16:06:29 +0200
......@@ -24,9 +24,9 @@ the file.
2. When installing code written by someone else, the ChangeLog entry
should be in the name of the author of the code, not the person who
installs it. I think it is helpful to put the author (if not yourself)
in the CVS log as well; and to not install any of your own changes in
the same commit.
installs it. I think it is helpful to put the author (if not yourself)
in the commit log as well (you can also use bzr commit's "--author"
option); and to not install any of your own changes in the same commit.
3. With images, add the legal info to a README file in the directory
containing the image.
......@@ -38,17 +38,17 @@ legal notices, consider if you should add a copyright statement.
right thing to do.
Every non-trivial file distributed through the Emacs CVS should be
Every non-trivial file distributed through the Emacs repository should be
self-explanatory in terms of copyright and license. This includes
files that are not distributed in Emacs releases (for example, the
admin/ directory), because the whole Emacs CVS is publicly
admin/ directory), because the whole Emacs repository is publicly
available.
The definition of triviality is a little vague, but a rule of thumb is
that any file with less than 15 lines of actual content is trivial. If
a file is auto-generated (eg ldefs-boot.el) from another one in the
CVS, then it does not really matter about adding a copyright statement
to the generated file.
repository, then it does not really matter about adding a copyright
statement to the generated file.
Legal advice says that we could, if we wished, put a license notice
even in trivial files, because copyright law in general looks at the
......@@ -67,8 +67,8 @@ file "years" in this directory). The PDF versions of refcards etc
should display copyright notices (an exception to the rule about
"generated" files), but these can just display the latest year. The
full list of years should be kept in comments in the source file. If
these are distributed in CVS, check in a regenerated version when the
tex files are updated.
these are distributed in the repository, check in a regenerated
version when the tex files are updated.
Copyright changes should be propagated to any associated repositories
(eg Gnus, MH-E), but I think in every case this happens automatically
......@@ -115,7 +115,7 @@ author should be removed and the year(s) transferred to the FSF); or
else it is possible the file should not be in Emacs at all (please
report!).
Note that it seems painfully clear that one cannot rely on CVS logs,
Note that it seems painfully clear that one cannot rely on commit logs,
or even ChangeLogs, for older changes. People often installed changes
from others, without recording the true authorship.
......@@ -555,10 +555,10 @@ system)
obviously good):
Is it OK to just `cvs remove' a file for legal reasons, or is
Is it OK to just `bzr remove' a file for legal reasons, or is
something more drastic needed? A removed file is still available from
CVS, if suitable options are applied. (This CVS issue obviously does
not affect a release).
the repository, if suitable options are applied. (This issue obviously
does not affect a release).
rms: will ask lawyer
......@@ -600,7 +600,7 @@ The EMACS_22_BASE branch was changed to GPLv3 (or later) 2007/07/25.
Some notes:
(see http://lists.gnu.org/archive/html/emacs-devel/2007-07/msg01431.html)
1. There are some files in Emacs CVS which are not part of Emacs (eg
1. There are some files in the Emacs tree which are not part of Emacs (eg
those included from Gnulib). These are all copyright FSF and (at time
of writing) GPL >= 2. rms says may as well leave the licenses of these
alone (may import them from Gnulib again). These are:
......
http://lists.gnu.org/archive/html/emacs-devel/2007-12/msg01208.html
From: Eli Zaretskii
Subject: Re: Log messages in CVS
Date: Sat, 29 Dec 2007 16:06:29 +0200
I once posted a summary that I know about; see:
http://lists.gnu.org/archive/html/emacs-devel/2006-11/msg00229.html
http://lists.gnu.org/archive/html/emacs-devel/2006-11/msg00234.html
http://lists.gnu.org/archive/html/emacs-devel/2006-11/msg00312.html
Richard commented here, basically approving my summary:
http://lists.gnu.org/archive/html/emacs-devel/2006-11/msg00276.html
2010-01-17 Chong Yidong <cyd@stupidchicken.com>
* elisp.texi: Remove duplicate edition information (Bug#5407).
2010-01-17 Juanma Barranquero <lekktu@gmail.com>
* two.el (volume-header-toc-markup): Fix typos in docstring.
2010-01-04 Stefan Monnier <monnier@iro.umontreal.ca>
Avoid dubious uses of save-excursions.
......
......@@ -100,9 +100,6 @@ Cover art by Etienne Suvasa.
@node Top, Introduction, (dir), (dir)
@top Emacs Lisp
This Info file contains edition @value{VERSION} of the GNU Emacs Lisp
Reference Manual, corresponding to GNU Emacs version @value{EMACSVER}.
@insertcopying
@end ifnottex
......
......@@ -54,8 +54,8 @@ Then run texindex on that file and save."
(defun volume-header-toc-markup ()
"Insert Volume I and Volume II text into .toc file.
NOTE: this auxilary function is file specific.
This is for the *Elisp Ref Manual*"
NOTE: this auxiliary function is file specific.
This is for the *Elisp Ref Manual*."
(interactive)
(goto-char (point-min))
(insert "\\unnumbchapentry {Volume 1}{}\n\\unnumbchapentry {}{}\n")
......
2010-01-17 Chong Yidong <cyd@stupidchicken.com>
* semantic.texi: Add Richard Y. Kim credit.
* eieio.texi (Making New Objects): Fix typo (Bug#5406).
2010-01-17 Michael Albinus <michael.albinus@gmx.de>
* tramp.texi (Frequently Asked Questions): Add GNU Emacs 23 and
SXEmacs 22 to the supported systems. New item for hung ssh sessions.
2010-01-17 Glenn Morris <rgm@gnu.org>
* calc.texi (Reporting Bugs): Don't mention format of repository.
* woman.texi (Bugs): Make "Emacs repository" less specific,
and the URL for same more specific.
* faq.texi (Latest version of Emacs): The repository is now Bazaar.
2010-01-17 Juanma Barranquero <lekktu@gmail.com>
* ede.texi (ede-step-project, ede-proj-target):
* tramp.texi (Remote processes): Fix typos.
2010-01-16 Mario Lang <mlang@delysid.org>
* ede.texi (ede-target):
* org.texi (Refiling notes): Remove duplicated words.
2010-01-04 Stefan Monnier <monnier@iro.umontreal.ca>
* gnus.texi (Posting Styles): Use with-current-buffer.
......
......@@ -35269,7 +35269,7 @@ to work on these, please send a message (using @kbd{M-x report-calc-bug})
so any efforts can be coordinated.
 
The latest version of Calc is available from Savannah, in the Emacs
CVS tree. See @uref{http://savannah.gnu.org/projects/emacs}.
repository. See @uref{http://savannah.gnu.org/projects/emacs}.
 
@c [summary]
@node Summary, Key Index, Reporting Bugs, Top
......@@ -1728,7 +1728,7 @@ The variable GNUSTEP_INSTALLATION_DOMAIN is set at this value.
Type: @code{(or null list)} @*
Default Value: @code{(quote ("GNUmakefile.preamble"))}
The auxilliary makefile for additional variables.
The auxiliary makefile for additional variables.
Included just before the specific target files.
@refill
......@@ -1736,7 +1736,7 @@ Included just before the specific target files.
Type: @code{(or null list)} @*
Default Value: @code{(quote ("GNUmakefile.postamble"))}
The auxilliary makefile for additional rules.
The auxiliary makefile for additional rules.
Included just after the specific target files.
@refill
......@@ -1968,7 +1968,7 @@ Retrieves the slot @code{sourcetype} from an object of class @code{ede-target}
@deffn Method ede-expand-filename :AFTER this filename &optional force
Return a fully qualified file name based on target @var{THIS}.
@var{FILENAME} should a a filename which occurs in a directory in which @var{THIS} works.
@var{FILENAME} should be a filename which occurs in a directory in which @var{THIS} works.
Optional argument @var{FORCE} forces the default filename to be provided even if it
doesn't exist.
@end deffn
......@@ -2083,7 +2083,7 @@ Relative to the path of the project it belongs to.
Type: @code{list} @*
Default Value: @code{nil}
Auxilliary source files included in this target.
Auxiliary source files included in this target.
Each of these is considered equivalent to a source file, but it is not
distributed, and each should have a corresponding rule to build it.
@refill
......
......@@ -645,7 +645,7 @@ function of @code{:initform}.
@comment node-name, next, previous, up
@chapter Making New Objects
Suppose we have defined a simple class is defined, such as:
Suppose we have a simple class is defined, such as:
@example
(defclass record ()
......
......@@ -1008,9 +1008,7 @@ conventions}).
@cindex Latest version of Emacs
@cindex Development, Emacs
@cindex Repository, Emacs
@cindex CVS repository, Emacs
@cindex Arch repository, Emacs
@cindex Git repository, Emacs
@cindex Bazaar repository, Emacs
Emacs @value{VER} is the current version as of this writing. A version
number with two components (e.g. @samp{22.1}) indicates a released
......@@ -1020,9 +1018,8 @@ version (e.g. @samp{23.0.50} is what will eventually become @samp{23.1}).
Emacs is under active development, hosted at
@uref{http://savannah.gnu.org/projects/emacs/, Savannah}. The source
code can be retrieved anonymously following the
@uref{http://savannah.gnu.org/cvs/?group=emacs, instructions}.
The primary repository is CVS, but Arch and Git mirrors are also
available.
@uref{http://savannah.gnu.org/bzr/?group=emacs, instructions}.
The repository is GNU Bazaar.
Because Emacs undergoes many changes before a release, the version
number of a development version is not especially meaningful. It is
......
......@@ -6181,7 +6181,7 @@ See the variable @code{org-refile-targets} for details. If you would like to
select a location via a file-path-like completion along the outline path, see
the variables @code{org-refile-use-outline-path} and
@code{org-outline-path-complete-in-steps}. If you would like to be able to
create new nodes as new parents for for refiling on the fly, check the
create new nodes as new parents for refiling on the fly, check the
variable @code{org-refile-allow-creating-parent-nodes}.
@kindex C-u C-c C-w
@item C-u C-c C-w
......
\input texinfo
@setfilename ../../info/semantic
@set TITLE Semantic Manual
@set AUTHOR Eric M. Ludlam and David Ponce
@set AUTHOR Eric M. Ludlam, David Ponce, and Richard Y. Kim
@settitle @value{TITLE}
@c *************************************************************************
......
No preview for this file type
......@@ -4,7 +4,7 @@
@settitle WoMan: Browse Unix Manual Pages ``W.O. (without) Man''
@c FIXME
@c Manual last updated:
@set UPDATED Time-stamp: <2009-02-16 09:25:50 karl>
@set UPDATED Time-stamp: <Sat 16-Jan-2010 19:18:43 gm on grasmoor>
@c Software version:
@set VERSION 0.54 (beta)
@afourpaper
......@@ -18,8 +18,8 @@
This file documents WoMan: A program to browse Unix manual pages `W.O.
(without) man'.
Copyright @copyright{} 2001, 2002, 2003, 2004,
2005, 2006, 2007, 2008, 2009, 2010 Free Software Foundation, Inc.
Copyright @copyright{} 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008,
2009, 2010 Free Software Foundation, Inc.
@quotation
Permission is granted to copy, distribute and/or modify this document
......@@ -1319,8 +1319,8 @@ inelegantly, then please
@enumerate
@item
try the latest version of @file{woman.el} from the Emacs CVS repository
on @uref{http://savannah.gnu.org/}. If it still fails, please
try the latest version of @file{woman.el} from the Emacs repository
on @uref{http://savannah.gnu.org/projects/emacs/}. If it still fails, please
@item
send a bug report to @email{bug-gnu-emacs@@gnu.org} and to
......
2010-01-16 Mario Lang <mlang@delysid.org>
* srecode/doc-cpp.srt, srecode/doc-default.srt:
* srecode/doc-java.srt: Remove duplicated words.
2010-01-14 Nick Roberts <nickrob@snap.net.nz>
* etc/images/gud/recstart.xpm, etc/images/gud/recstop.xpm:
......
......@@ -58,7 +58,7 @@ Recycle doxygen comment code from the more general template set."
----
template group-comment-end :blank :indent
"A comment occurring at the end of a a group of declarations.
"A comment occurring at the end of a group of declarations.
Recycle doxygen comment code from the more general template set."
----
{{>:classdecl:doxygen-function-group-end}}
......@@ -75,7 +75,7 @@ Recycle doxygen comment code from the more general template set."
----
template group-comment-end :blank :indent
"A comment occurring at the end of a a group of declarations.
"A comment occurring at the end of a group of declarations.
Recycle doxygen comment code from the more general template set."
----
{{>:classdecl:doxygen-function-group-end}}
......
......@@ -57,7 +57,7 @@ template group-comment-start :blank :indent
----
template group-comment-end :indent
"A comment occurring at the end of a a group of declarations."
"A comment occurring at the end of a group of declarations."
----
{{comment_start}} End {{?GROUPNAME}} {{comment_end}}
----
......@@ -72,7 +72,7 @@ template group-comment-start :blank :indent
----
template group-comment-end :indent
"A comment occurring at the end of a a group of declarations."
"A comment occurring at the end of a group of declarations."
----
{{>:declaration:group-comment-end}}
----
......
......@@ -59,7 +59,7 @@ Recycle javadoc comment code from the more general template set."
----
template group-comment-end :blank :indent
"A comment occurring at the end of a a group of declarations.
"A comment occurring at the end of a group of declarations.
Recycle javadoc comment code from the more general template set."
----
{{>:classdecl:javadoc-function-group-end}}
......@@ -76,7 +76,7 @@ Recycle javadoc comment code from the more general template set."
----
template group-comment-end :blank :indent
"A comment occurring at the end of a a group of declarations.
"A comment occurring at the end of a group of declarations.
Recycle javadoc comment code from the more general template set."
----
{{>:classdecl:javadoc-function-group-end}}
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment