From: Pete Harlan <pgit@pcharlan•com>
To: git@vger•kernel.org
Subject: Archiving tags/branches?
Date: Fri, 17 Oct 2008 18:43:46 -0700 [thread overview]
Message-ID: <48F93F52.4070506@pcharlan.com> (raw)
Hi,
I'm looking for a way to manage an ever-growing list of tags. I've read
some git docs, but am new to git and wonder if the below method doesn't
work or if there's a standard practice I haven't run into.
Most of the tags in my repo are uninteresting to look at, but can't be
deleted. (Code releases for the most part, or stalled topic branches.)
If I wanted to archive those, it looks like this would work:
mkdir .git/refs/archived-tags
cp -a .git/refs/tags/* .git/refs/archived-tags
git tag -d <tag-to-hide> # repeat as necessary
I can then maintain a short list of tags that currently interest me, but
am guaranteed not to lose old branches (say) referenced by those tags.
Is there a reason this won't work?
The immediate downsides I see are:
1. The name "archived-tags" might clash someday with a git directory.
2. I have to manually copy this to clones if I want it there too, and
can't manage it from them remotely.
In general, I'm thinking flat tag and branch namespaces must get
unweildy, and short of implementing directory-style namespace management
within git (e.g., hide tags beginning with "." by default, allow tag
subdirectories) I'm looking for a workaround.
Thanks,
--Pete
next reply other threads:[~2008-10-18 1:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-18 1:43 Pete Harlan [this message]
2008-10-18 2:50 ` Archiving tags/branches? 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
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=48F93F52.4070506@pcharlan.com \
--to=pgit@pcharlan$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox