diff options
| author | Tom Tromey <tromey@redhat.com> | 2013-08-12 14:04:37 -0600 |
|---|---|---|
| committer | Tom Tromey <tromey@sourceware.org> | 2013-10-25 14:02:58 +0000 |
| commit | 20cef68c2f93d4421565fa0aad4fa51db4f50ff7 (patch) | |
| tree | eab5411382778c6293d0757b46e46925ea0da36a /binutils/MAINTAINERS | |
| parent | c8f8fedd3cd6a6937c44ff483e9c715548039a73 (diff) | |
| download | gdb-20cef68c2f93d4421565fa0aad4fa51db4f50ff7.zip gdb-20cef68c2f93d4421565fa0aad4fa51db4f50ff7.tar.gz gdb-20cef68c2f93d4421565fa0aad4fa51db4f50ff7.tar.bz2 | |
binutils doc update
Here's another small patch to lay the groundwork for the git
conversion. This one updates the BFD and binutils documentation for
the move.
bfd:
* doc/bfdint.texi (BFD generated files): Mention git, not cvs.
binutils:
* MAINTAINERS: Mention git, not cvs.
* README: Mention git, not cvs.
Diffstat (limited to 'binutils/MAINTAINERS')
| -rw-r--r-- | binutils/MAINTAINERS | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/binutils/MAINTAINERS b/binutils/MAINTAINERS index 3ea3685..f3ecf09 100644 --- a/binutils/MAINTAINERS +++ b/binutils/MAINTAINERS @@ -252,20 +252,20 @@ would be appropriate if the branch was created on January 1st, 2005. Having selected the branch name, create the branch as follows: -1. Check out binutils, so that you have a CVS checkout corresponding +1. Check out binutils, so that you have a git checkout corresponding to the initial state of your branch. 2. Create a tag: - cvs tag binutils-<org>-<name>-branchpoint + git tag binutils-<org>-<name>-branchpoint That tag will allow you, and others, to easily determine what's changed on the branch relative to the initial state. -3. Create the branch: +3. Create and push the branch: - cvs rtag -b -r binutils-<org>-<name>-branchpoint \ - binutils-<org>-<name>-branch + git checkout -b binutils-<org>-<name>-branch + git push origin HEAD 4. Document the branch: |