<title>Check-in Names</title>
Many Fossil commands and [./webui.wiki | web-interface] URLs accept
check-in names as an argument. For example, the "info" command
accepts an optional check-in name to identify the specific checkout
about which information is desired:
<blockquote>
<tt>fossil info</tt> <i>checkin-name</i>
</blockquote>
................................................................................
The space between the day and the year can optionally be
replaced by an uppercase <b>T</b> and the entire timestamp can
optionally be followed by "<b>utc</b>".
In its default configuration, Fossil interprets and displays all dates
in Universal Coordinated Time (UTC). This tends to work the best for
distributed projects where participants are scattered around the globe.
But there is an open on the Admin/Timeline page of the web-interface to
switch to local time. The "<b>utc</b>" suffix on an timestamp check-in
name is meaningless if Fossil is in the default mode of using UTC for
everything, but if Fossil has been switched to localtime mode, then the
"<b>utc</b>" suffix means to interpret that particular timestamp using
UTC instead localtime.
As an example, consider the homepage for the Fossil website itself:

<title>Check-in Names</title>
Many Fossil [/help|commands] and [./webui.wiki | web-interface] URLs accept
check-in names as an argument. For example, the "[/help/info|info]" command
accepts an optional check-in name to identify the specific checkout
about which information is desired:
<blockquote>
<tt>fossil info</tt> <i>checkin-name</i>
</blockquote>
................................................................................
The space between the day and the year can optionally be
replaced by an uppercase <b>T</b> and the entire timestamp can
optionally be followed by "<b>utc</b>".
In its default configuration, Fossil interprets and displays all dates
in Universal Coordinated Time (UTC). This tends to work the best for
distributed projects where participants are scattered around the globe.
But there is an option on the Admin/Timeline page of the web-interface to
switch to local time. The "<b>utc</b>" suffix on an timestamp check-in
name is meaningless if Fossil is in the default mode of using UTC for
everything, but if Fossil has been switched to localtime mode, then the
"<b>utc</b>" suffix means to interpret that particular timestamp using
UTC instead localtime.
As an example, consider the homepage for the Fossil website itself:

should understand that whenever "src.c" or "src.h" is used in the text
that follows, we really mean all (79) other source files other than
the exceptions described above.
<h1>3.0 Automatically generated files</h1>
The "VERSION.h" header file contains some C preprocessor macros that
identify the version of Fossil that is to be build. The VERSION.h file
generated automatically from information extracted from the "manifest"
and "manifest.uuid" source files in the root directory of the source tree.
(The "manifest" and "manifest.uuid" files are automatically generated and
updated by Fossil itself. See the [/help/setting | fossil set manifest]
command for additional information.)
Under unix, there is an AWK script that converts manifest and manifest.uuid
................................................................................
in the root of the source tree are the first two arguments and the name of
the generated VERSION.h file is the third and final argument.
<h1>4.0 Preprocessing</h1>
There are three preprocessors for the Fossil sources. The mkindex
and translate preprocessors can be run in any order. The makeheaders
preprocessor has to be run after translate.
<h2>4.1 The mkindex preprocessor</h2>
The mkindex program scans the "src.c" source files looking for special
comments that identify routines that implement of various Fossil commands,
web interface methods, and help text comments. The mkindex program
generates some C code that Fossil uses in order to dispatch commands and

should understand that whenever "src.c" or "src.h" is used in the text
that follows, we really mean all (79) other source files other than
the exceptions described above.
<h1>3.0 Automatically generated files</h1>
The "VERSION.h" header file contains some C preprocessor macros that
identify the version of Fossil that is to be build. The VERSION.h file is
generated automatically from information extracted from the "manifest"
and "manifest.uuid" source files in the root directory of the source tree.
(The "manifest" and "manifest.uuid" files are automatically generated and
updated by Fossil itself. See the [/help/setting | fossil set manifest]
command for additional information.)
Under unix, there is an AWK script that converts manifest and manifest.uuid
................................................................................
in the root of the source tree are the first two arguments and the name of
the generated VERSION.h file is the third and final argument.
<h1>4.0 Preprocessing</h1>
There are three preprocessors for the Fossil sources. The mkindex
and translate preprocessors can be run in any order. The makeheaders
preprocessor must be run after translate.
<h2>4.1 The mkindex preprocessor</h2>
The mkindex program scans the "src.c" source files looking for special
comments that identify routines that implement of various Fossil commands,
web interface methods, and help text comments. The mkindex program
generates some C code that Fossil uses in order to dispatch commands and

This page was generated in about
0.007s by
Fossil 2.8 [246f249e5a] 2019-01-21 20:07:41