diff options
Diffstat (limited to 'gdb/doc/gdbint.texinfo')
| -rw-r--r-- | gdb/doc/gdbint.texinfo | 34 |
1 files changed, 17 insertions, 17 deletions
diff --git a/gdb/doc/gdbint.texinfo b/gdb/doc/gdbint.texinfo index 749e121332b..60805adfa68 100644 --- a/gdb/doc/gdbint.texinfo +++ b/gdb/doc/gdbint.texinfo @@ -6677,7 +6677,7 @@ Specific Information, gdb, Debugging with @value{GDBN}}). @section Versions @value{GDBN}'s version is determined by the file -@file{gdb/common/version.in} and takes one of the following forms: +@file{gdb/version.in} and takes one of the following forms: @table @asis @item @var{major}.@var{minor} @@ -6781,7 +6781,7 @@ branch tag, denoting the head of the branch, does not need this.} @cindex vendor branches To avoid version conflicts, vendors are expected to modify the file -@file{gdb/common/version.in} to include a vendor unique alphabetic identifier +@file{gdb/version.in} to include a vendor unique alphabetic identifier (an official @value{GDBN} release never uses alphabetic characters in its version identifier). E.g., @samp{6.2widgit2}, or @samp{6.2 (Widgit Inc Patch 2)}. @@ -6830,7 +6830,7 @@ The @value{GDBN} module @code{gdb} should be specified when creating a branch (branches of individual files should be avoided). @xref{Tags}. @item a branch shall be branded using @file{version.in} -The file @file{gdb/common/version.in} shall be modified so that it identifies +The file @file{gdb/version.in} shall be modified so that it identifies the branch @var{owner} and branch @var{name}, e.g., @samp{6.2.50.20030303_owner_name} or @samp{6.2 (Owner Name)}. @@ -7108,16 +7108,16 @@ $ echo $u $v$V 5.1 5_2 $ cd /tmp $ echo cvs -f -d :ext:sourceware.org:/cvs/src co \ --r gdb_$V-branch src/gdb/common/version.in +-r gdb_$V-branch src/gdb/version.in cvs -f -d :ext:sourceware.org:/cvs/src co - -r gdb_5_2-branch src/gdb/common/version.in + -r gdb_5_2-branch src/gdb/version.in $ ^echo ^^ -U src/gdb/common/version.in +U src/gdb/version.in $ cd src/gdb -$ echo $u.90-DATE-cvs > common/version.in -$ cat common/version.in +$ echo $u.90-DATE-cvs > version.in +$ cat version.in 5.1.90-DATE-cvs -$ cvs -f commit common/version.in +$ cvs -f commit version.in @end smallexample @itemize @bullet @@ -7317,18 +7317,18 @@ to get it updated.} @file{INSTALL} from the core documentation. This might be worth pursuing.} -@item gdb/common/version.in +@item gdb/version.in @smallexample -$ echo $v > gdb/src/gdb/common/version.in -$ cat gdb/src/gdb/common/version.in +$ echo $v > gdb/src/gdb/version.in +$ cat gdb/src/gdb/version.in 5.2 -$ emacs gdb/src/gdb/common/version.in +$ emacs gdb/src/gdb/version.in ... c-x 4 a ... Bump to version ... c-x c-s c-x c-c -$ cp gdb/src/gdb/common/version.in insight/src/gdb/common/version.in +$ cp gdb/src/gdb/version.in insight/src/gdb/version.in $ cp gdb/src/gdb/ChangeLog insight/src/gdb/ChangeLog @end smallexample @@ -7573,7 +7573,7 @@ In particular you'll need to commit any changes to: @item @file{gdb/ChangeLog} @item -@file{gdb/common/version.in} +@file{gdb/version.in} @item @file{gdb/NEWS} @item @@ -7600,9 +7600,9 @@ Insight is used since that contains more of the release than Just put something in the @file{ChangeLog} so that the trunk also indicates when the release was made. -@subsubheading Restart @file{gdb/common/version.in} +@subsubheading Restart @file{gdb/version.in} -If @file{gdb/common/version.in} does not have the string @samp{DATE} then +If @file{gdb/version.in} does not have the string @samp{DATE} then builds will not include the checkout date in their resulting version. Having committed all the release changes it can be set to @file{5.2.0_DATE-cvs} which will restart things. |