Searched refs:branchpoint (Results 1 – 9 of 9) sorted by relevance
4710 char *branchpoint, *newrevnum; local4718 branchpoint = xstrdup (branch);4729 free (branchpoint);4732 free (branchpoint);6061 char *branchpoint = NULL; local6192 rev1 = xstrdup (branchpoint);6193 if (numdots (branchpoint) > 1)6241 bp = strrchr (branchpoint, '.');6245 before = xstrdup (branchpoint);6511 if (branchpoint != NULL)[all …]
663 * rcs.c (RCS_delete_revs): If "rev1" equals "branchpoint", then set
3727 the branchpoint owned by someone else, leave it alone. This
233 cvs tag binutils-<org>-<name>-branchpoint240 cvs rtag -b -r binutils-<org>-<name>-branchpoint \
176 to the branchpoint, and then from the branchpoint to the head of the
832 containing REV and REV itself. The branchpoint and REV are
3841 @c having a tag on the branchpoint. For example3842 @c "cvs tag rel-1-0-patches-branchpoint" before8377 branchpoint and @var{rev} are left intact. For8928 @c FIXME: Should we be recommending tagging the branchpoint?8943 @c FIXME: Should we be recommending tagging the branchpoint?
3057 should better document tagging the branchpoint.
5463 gdb_@var{major}_@var{minor}-@var{YYYY}@var{MM}@var{DD}-branchpoint5469 release is made, both the branchpoint and release tags include the5540 @item @var{owner}_@var{name}-@var{YYYYMMDD}-branchpoint5546 cvs rtag @var{owner}_@var{name}-@var{YYYYMMDD}-branchpoint gdb5547 cvs rtag -b -r @var{owner}_@var{name}-@var{YYYYMMDD}-branchpoint \5558 -j@var{owner}_@var{name}-@var{YYYYMMDD}-branchpoint5716 -D $D-gmt gdb_$V-$D-branchpoint insight+dejagnu5718 -D 2002-03-03-gmt gdb_5_2-2002-03-03-branchpoint insight+dejagnu5722 -b -r gdb_$V-$D-branchpoint gdb_$V-branch insight+dejagnu5724 -b -r gdb_5_2-2002-03-03-branchpoint gdb_5_2-branch insight+dejagnu