All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: "SZEDER Gábor" <szeder@ira.uka.de>, "Pete Harlan" <pgit@pcharlan.com>
Subject: Re: Archiving tags/branches?
Date: Sat, 18 Oct 2008 15:32:59 +0200	[thread overview]
Message-ID: <200810181532.59883.johan@herland.net> (raw)
In-Reply-To: <20081018130204.GB3749@neumann>

On Saturday 18 October 2008, SZEDER Gábor wrote:
> On Sat, Oct 18, 2008 at 01:15:49PM +0200, Johan Herland wrote:
> > Go have a look in .git/packed-refs. Then have a read through
> > git-pack-refs(1).
>
> Oh, indeed, my good old refs are there!  Thanks for the info.

BTW, the best way IMHO to archive old refs is to clone your repo (with all 
tags/branches) to a backup disk, and then regularly push (git push --all && 
git push --tags) your new tags/branches to this backup. You are now free to 
delete these tags/branches from your work repo (they will not be deleted 
from the backup unless you use "git push --mirror"). And if you ever need 
to retrieve an old tag/branch, it's just a matter of pulling it from the 
backup repo. Nice, clean, flexible, and requires no changes to git.


Have fun! :)

...Johan

-- 
Johan Herland, <johan@herland.net>
www.herland.net

  reply	other threads:[~2008-10-18 13:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-18  1:43 Archiving tags/branches? Pete Harlan
2008-10-18  2:50 ` David Symonds
2008-10-20  6:14   ` Pete Harlan
2008-10-18 10:23 ` SZEDER Gábor
2008-10-18 11:15   ` Johan Herland
2008-10-18 13:02     ` SZEDER Gábor
2008-10-18 13:32       ` Johan Herland [this message]
2008-10-20  6:36         ` Pete Harlan
2008-10-20  7:53           ` Johan Herland
2008-10-21  2:53             ` Pete Harlan
2008-10-20 14:35           ` Jakub Narebski
2008-10-21  4:08             ` Pete Harlan
2008-10-21  8:15               ` Jakub Narebski
2008-10-21  9:33                 ` Pete Harlan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200810181532.59883.johan@herland.net \
    --to=johan@herland.net \
    --cc=git@vger.kernel.org \
    --cc=pgit@pcharlan.com \
    --cc=szeder@ira.uka.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.