view admin/notes/BRANCH @ 102670:06ca3efb355b

inc/sys/stat.h (struct stat): Change the types of st_uid and st_gid to unsigned. inc/pwd.h (struct passwd): Change the types of pw_uid and pw_gid to unsigned. (getpwuid): Argument is now unsigned. uid_t is now unsigned. ntlib.c (setuid): Argument is now unsigned. (getuid): Return value is now unsigned. (getpwuid): Argument is now unsigned. (fchown): UID and GID arguments are now unsigned. ntlib.h (fchown): UID and GID arguments are now unsigned. (getuid): Return value is now unsigned. (setuid): Argument is now unsigned. (getpwuid): Remove prototype (it's declared in nt/inc/pwd.h). w32.c (getpwuid): Change argument type to unsigned. (struct w32_id): Change type of `rid' member to unsigned. (w32_cached_id, w32_add_to_cache, get_name_and_id): Change type of argument ID to unsigned. All callers changed. (getuid, geteuid, getgid, getegid): Change return type to unsigned.

This file describes the CVS 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.

Emacs development takes place on the trunk.  Most of the time, Emacs
hackers add to it relatively free of constraint (aside from proper
legal / accounting practices), although sometimes there is related
discussion on the emacs-devel mailing list.

Sometime before the release of a new major version of Emacs (eg 22.1),
a "feature freeze" is imposed on the trunk.  No new features may be
added after this point.  This is usually many months before the release.
During this time, there is no official place for development of new features.

Shortly before the release, a release branch is created.  For example,
EMACS_22_BASE or EMACS_21_1_RC for Emacs 22.x and 21.x, respectively.
(Unfortunately the naming scheme has not always been consistent.)

The release branch is used to make the release (22.1), and all later
members of the series (22.2, 22.3, etc).  Generally, only bug-fixes have
been allowed in the minor releases, although in 22.x, self-contained
new features were allowed on a case-by-case basis.

From the point that a release branch is created, the trunk is free for
development for the next major version.