Robert Harker Technical Wiki
Thoughts and Ideas About Large Sites

[ Prev ] [ Index ] [ Next ]

Git openstack docs

TOPIC

Date: Wed, 11 Sep 2013 22:23:25 -0500
From: Anne Gentle <anne@openstack.org>
To: "openstack-docs@lists.openstack.org"
Subject: [Openstack-docs] Need to retrieve old files? No worries

I'm working on ensuring that some Identity configuration info is correctly
placed, so I wanted a copy of the repository before the rename. Here's how
you do that in case you ever need to get an "archived" copy of the repo.

  1. Switch into a temporary directory.

  1. Clone the openstack-manuals repository.
$ git clone http://github.com/openstack/openstack-manuals.git
Cloning into 'openstack-manuals'...
remote: Counting objects: 30034, done.
remote: Compressing objects: 100% (9438/9438), done.
remote: Total 30034 (delta 17276), reused 26918 (delta 14505)
Receiving objects: 100% (30034/30034), 55.18 MiB | 990 KiB/s, done.
Resolving deltas: 100% (17276/17276), done.

  1. Go to review.openstack.org and look for the patch that occured just
before the rename patch. (It's https://review.openstack.org/#/c/45491/).

  1. On that page, click the "checkout" tab and then copy the long git
command to checkout that exact patch.

  1. Switch into the openstack-manuals directory and paste that command:
$ cd openstack-manuals
$ git fetch https://review.openstack.org/openstack/openstack-manualsrefs/changes/91/45491/4
&& git checkout FETCH_HEAD
>From https://review.openstack.org/openstack/openstack-manuals
Note: checking out 'FETCH_HEAD'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b new_branch_name

HEAD is now at d5bcc13... Add HSTS and cookie security to dashboard example
config

Now I have copies of the files I need and I can carefully copy them into
the working directory to make a new patch.

Backlinks: index Start
Created with Zim desktop wiki