Preparing for git transition; replace bzr-specific language.

diff --git a/admin/notes/copyright b/admin/notes/copyright
index 77ca913701564b90a3d9663bc1b22bca9d847876..109126a30625f4ccb35ef945d8632151df1dddbe 100644 (file)
--- a/admin/notes/copyright
+++ b/admin/notes/copyright
@@ -24,7 +24,7 @@ the file.
 
 2. When installing code written by someone else, the ChangeLog entry
 should be in the name of the author of the code, not the person who
-installs it.  Also use bzr commit's "--author" option.
+installs it.  Also use commit's "--author" option.
 Do not install any of your own changes in the same commit.
 
 3. With images, add the legal info to a README file in the directory
@@ -484,10 +484,10 @@ system)
     obviously good):
 
 
-Is it OK to just `bzr remove' a file for legal reasons, or is
-something more drastic needed? A removed file is still available from
-the repository, if suitable options are applied. (This issue obviously
-does not affect a release).
+Is it OK to just remove a file for legal reasons, or is something more
+drastic (excision from the entire repository history) needed? A
+removed file is still available from the repository, if suitable
+options are applied. (This issue obviously does not affect a release).
   rms: will ask lawyer