aboutsummaryrefslogtreecommitdiffstats
path: root/admin
diff options
context:
space:
mode:
Diffstat (limited to 'admin')
-rw-r--r--admin/notes/copyright10
1 files changed, 5 insertions, 5 deletions
diff --git a/admin/notes/copyright b/admin/notes/copyright
index 77ca9137015..109126a3062 100644
--- a/admin/notes/copyright
+++ b/admin/notes/copyright
@@ -24,7 +24,7 @@ the file.
24 24
252. When installing code written by someone else, the ChangeLog entry 252. When installing code written by someone else, the ChangeLog entry
26should be in the name of the author of the code, not the person who 26should be in the name of the author of the code, not the person who
27installs it. Also use bzr commit's "--author" option. 27installs it. Also use commit's "--author" option.
28Do not install any of your own changes in the same commit. 28Do not install any of your own changes in the same commit.
29 29
303. With images, add the legal info to a README file in the directory 303. With images, add the legal info to a README file in the directory
@@ -484,10 +484,10 @@ system)
484 obviously good): 484 obviously good):
485 485
486 486
487Is it OK to just `bzr remove' a file for legal reasons, or is 487Is it OK to just remove a file for legal reasons, or is something more
488something more drastic needed? A removed file is still available from 488drastic (excision from the entire repository history) needed? A
489the repository, if suitable options are applied. (This issue obviously 489removed file is still available from the repository, if suitable
490does not affect a release). 490options are applied. (This issue obviously does not affect a release).
491 rms: will ask lawyer 491 rms: will ask lawyer
492 492
493 493