From: Joe Perches <joe@perches.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next <linux-next@vger.kernel.org>
Subject: git tag expiry?
Date: Tue, 29 Nov 2011 10:22:52 -0800 [thread overview]
Message-ID: <1322590972.15134.5.camel@Joe-Laptop> (raw)
Hi Stephen.
In order to keep the next git repository size down,
are you going to continue to expire and delete older
next-<date> tags after some number of months/days/weeks?
I think it'd be sensible to keep a maximum of 2 months
of tags and once a month expire out the oldest tags
followed by a repack.
next reply other threads:[~2011-11-29 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 18:22 Joe Perches [this message]
2011-11-29 21:27 ` git tag expiry? Stephen Rothwell
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=1322590972.15134.5.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox