From: Sam Vilain <sam@vilain.net>
To: Mike Hommey <mh@glandium.org>
Cc: David Kastrup <dak@gnu.org>, git@vger.kernel.org
Subject: Re: Rewriting history with git-filter-branch and leaking objects (?)
Date: Sun, 19 Aug 2007 14:34:38 +1200 [thread overview]
Message-ID: <46C7AC3E.5010806@vilain.net> (raw)
In-Reply-To: <20070817174621.GA14503@glandium.org>
Mike Hommey wrote:
> Well, with the introduction of git-filter-branch, once you have
> rewritten your history and validated that everything is okay,
> you might mean to remove the original branch...
>
Right, but it's probably better to leave a trail. I tend to use
refs/Attic/* for branches that I've re-written (if I published them).
That way, nothing will send or receive them by default. Sometimes I'll
have a "clean" repository which doesn't have any of them for faster
initial cloning.
Sam.
next prev parent reply other threads:[~2007-08-19 2:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-17 17:18 Rewriting history with git-filter-branch and leaking objects (?) Mike Hommey
2007-08-17 17:34 ` David Kastrup
2007-08-17 17:46 ` Mike Hommey
2007-08-19 2:34 ` Sam Vilain [this message]
2007-08-17 21:11 ` Junio C Hamano
2007-08-17 18:31 ` Mike Hommey
2007-08-19 19:59 ` Mike Hommey
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=46C7AC3E.5010806@vilain.net \
--to=sam@vilain.net \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=mh@glandium.org \
/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;
as well as URLs for NNTP newsgroup(s).