[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] trunk r118200: Preparing for git transition; replace bzr-s
From: |
Eric S. Raymond |
Subject: |
[Emacs-diffs] trunk r118200: Preparing for git transition; replace bzr-specific language. |
Date: |
Sat, 25 Oct 2014 18:49:30 +0000 |
User-agent: |
Bazaar (2.6b2) |
------------------------------------------------------------
revno: 118200
revision-id: address@hidden
parent: address@hidden
committer: Eric S. Raymond <address@hidden>
branch nick: trunk
timestamp: Sat 2014-10-25 14:48:49 -0400
message:
Preparing for git transition; replace bzr-specific language.
modified:
admin/notes/copyright copyright-20091113204419-o5vbwnq5f7feedwu-4445
=== modified file 'admin/notes/copyright'
--- a/admin/notes/copyright 2014-08-09 16:12:33 +0000
+++ b/admin/notes/copyright 2014-10-25 18:48:49 +0000
@@ -24,7 +24,7 @@
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 @@
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
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Emacs-diffs] trunk r118200: Preparing for git transition; replace bzr-specific language.,
Eric S. Raymond <=