The other option is to use an orphan branch 

This keeps the parts independent while in the same repo, but using the tree 
sha1 you should be able to confirm where it came from. I believe you can use 
gitolite for access control to branches in the repo, but I've not used it.

[The tree sha1 is the sha1 has of the committed work tree, independent of any 
of the history, commit message or date information, so if you have the same 
(identical) directory content and file names at two different points in history 
they still have the same tree sha1]

  ----- Original Message ----- 
  From: Deanna Delapasse 
  To: Philip Oakley 
  Sent: Friday, June 14, 2013 2:23 PM
  Subject: Re: [git-users] Best way to "identify" a version of a repo

  Maybe - I'm very new to this.  I'll try it.

  On Fri, Jun 14, 2013 at 8:05 AM, Philip Oakley <> wrote:

    From: Deanna Delapasse 
      Sent: Friday, June 14, 2013 1:08 PM
      Subject: [git-users] Best way to "identify" a version of a repo

      I need to checkout code from a repo and somehow identify it (timestamp, 
hash, …) such that at some later time I can extract the SAME versions of all 
the code.

      I’m provisioning cloud instances, so each time would be a fresh “get 
clone” into an empty folder.  After I create the “master” (ie provision the 
FIRST instance) I need to record some way to identify it in case I have to 
recreate the master.I prefer NOT to alter the original repo (ie tag it), but 
prefer the ‘work’ of identifying the sources to be done on the client side.

      Would appreciate any guidance!


    Isn't the URL and sha1 sufficient? The URL gets you to the repo, and the 
sha1 gets the commit. You add the output of `git describe` to give a bit of 


  No virus found in this message.
  Checked by AVG -
  Version: 2013.0.3345 / Virus Database: 3199/6409 - Release Date: 06/13/13

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to