git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Archiving tags/branches?

From
Johan Herland <johan@herland.net>
Date
Oct 18, 2008, 13:32 UTC
Message-ID
<200810181532.59883.johan@herland.net>
In-Reply-To
<20081018130204.GB3749@neumann>
On Saturday 18 October 2008, SZEDER Gábor wrote:
Show 5 quoted lines
> 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
Previous: SZEDER GáborNext: Pete Harlan
Message 7 of 14 in “Archiving tags/branches?”
  1. Pete HarlanOct 18, 2008
  2. David SymondsOct 18, 2008
  3. Pete HarlanOct 20, 2008
  4. SZEDER GáborOct 18, 2008
  5. Johan HerlandOct 18, 2008
  6. SZEDER GáborOct 18, 2008
  7. Johan HerlandOct 18, 2008
  8. Pete HarlanOct 20, 2008
  9. Johan HerlandOct 20, 2008
  10. Pete HarlanOct 21, 2008
  11. Jakub NarebskiOct 20, 2008
  12. Pete HarlanOct 21, 2008
  13. Jakub NarebskiOct 21, 2008
  14. Pete HarlanOct 21, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.