Commit 98ecd485 authored by Brad King's avatar Brad King

Drop mention of Gerrit from instructions in third-party README files

Commits updating third-party libraries will no longer need a Gerrit
Change-Id.
parent 370a7eb1
......@@ -40,8 +40,7 @@ appropriate date and version number:
git commit --amend
Edit the commit message to describe the procedure used to obtain the
content. Be sure to add a gerrit change-id line to the bottom of the
message. Then push the changes back up to the main local repository:
content. Then push the changes back up to the main local repository:
git push .. HEAD:xdmf2vtk-upstream
cd ..
......
......@@ -47,9 +47,6 @@ content. Then push the changes back up to the main repository:
cd ..
rm -rf hdf5-tmp
Make sure your commit in 'hdf5-upstream' has a 'Change-Id: ...', otherwise
you won't be able to commit your change into gerrit.
Create a topic in the main repository on which to perform the update:
git checkout -b update-hdf5 master
......
......@@ -40,8 +40,7 @@ appropriate date and version number:
git commit --amend
Edit the commit message to describe the procedure used to obtain the
content. Be sure to add a Gerrit Change-Id line to the bottom of the
message. Then push the changes back up to the main local repository:
content. Then push the changes back up to the main local repository:
git push .. HEAD:netcdf-upstream
cd ..
......
......@@ -40,8 +40,7 @@ appropriate date and version number:
git commit --amend
Edit the commit message to describe the procedure used to obtain the
content. Be sure to add a Gerrit Change-Id line to the bottom of the
message. Then push the changes back up to the main local repository:
content. Then push the changes back up to the main local repository:
git push .. HEAD:verdict-upstream
cd ..
......
......@@ -40,8 +40,7 @@ appropriate date and version number:
git commit --amend
Edit the commit message to describe the procedure used to obtain the
content. Be sure to add a gerrit change-id line to the bottom of the
message. Then push the changes back up to the main local repository:
content. Then push the changes back up to the main local repository:
git push .. HEAD:xdmf2-upstream
cd ..
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment