diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2014-10-25 14:48:49 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2014-10-25 14:48:49 -0400 |
| commit | c1609a8ccefd965c582c1cbb478b288514540afb (patch) | |
| tree | 4e85a0b22d74ebb881208ab55964cc3edc79f36f | |
| parent | 3abb316834402a3f72f80bc4826b7bbe296c35e3 (diff) | |
| download | emacs-c1609a8ccefd965c582c1cbb478b288514540afb.tar.gz | |
Preparing for git transition; replace bzr-specific language.
| -rw-r--r-- | admin/notes/copyright | 10 |
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. 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 |