bk commit - mysqldoc@docsrva tree (stefan:1.2826)

[stefan]

Below is the list of changes that have just been committed into a local
mysqldoc repository of stefan. When stefan does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.2826 05/06/20 10:31:19 stefan@stripped +1 -0
  SYNC.TXT:
    new file

  refman/SYNC.TXT
    1.1 05/06/20 10:31:09 stefan@stripped +23 -0

  refman/SYNC.TXT
    1.0 05/06/20 10:31:09 stefan@stripped +0 -0
    BitKeeper file /home/stefan/bk/mysqldoc/refman/SYNC.TXT

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	stefan
# Host:	apollon.site
# Root:	/home/stefan/bk/mysqldoc
--- New file ---
+++ refman/SYNC.TXT	05/06/20 10:31:09
You can generate a patch by using bk diffs (or rather, bk diffs -u to get
unified format).  It's best to do this before checking in your changes,
because otherwise you'll have to mess around specifying revision numbers,
I think.

bk diffs -u file          Changes to given file
bk diffs -u               Change to all files in current directory

So the latter command gives you a quick overview of what edits you've
made and need to be applied in the 4.1/5.0 directories.

For example, I just made a few changes to stored-procedures.xml in refman.
I applied them to the other directories like this:

% bk diffs -u >junk
% cd ../refman-4.1
% patch < ../refman/junk
patching file stored-procedures.xml
% cd ../refman-5.0
% patch < ../refman/junk
patching file stored-procedures.xml

Then I check it all in with bk citool.