From: Wincent Colaiuta <win@wincent.com>
To: "Matthias Kestenholz" <lists@spinlock.ch>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Obliterating a commit
Date: Sun, 30 Sep 2007 16:13:17 +0200 [thread overview]
Message-ID: <57945943-2355-447D-9474-89834BADB312@wincent.com> (raw)
In-Reply-To: <1f6632e50709300515h57f4b4ffh9a18fef29b134f13@mail.gmail.com>
El 30/9/2007, a las 14:15, Matthias Kestenholz escribió:
> If you use ssh to push your changes (that is, you are not copying
> or rsyncing packfiles), only commits, trees and blobs, which are
> reachable
> through the DAG will be published. Commits and Blobs which are only
> reachable through your reflog are not published, since the reflog
> only applies
> to your local repository.
Ah, this is good to know. Yes, I do principally publish by pushing to
a central repo, but I wanted to really destroy the objects just in
case in the future I or somebody else ever clones my local repo.
> The simplest thing you could do is remove the reflog for HEAD and
> refs/heads/master respectively your current branch and run 'git prune'
> afterwards (if you have not repacked
> already, otherwise you'd need to run 'git repack -a -d' or 'git gc'
> to get
> rid of blobs inside your packfile.
Thanks very much, Matthias. Blowing away those reflogs and running
git-prune worked and it's doesn't require too much fiddling.
Cheers,
Wincent
prev parent reply other threads:[~2007-09-30 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-30 11:32 Obliterating a commit Wincent Colaiuta
2007-09-30 12:15 ` Matthias Kestenholz
2007-09-30 14:13 ` Wincent Colaiuta [this message]
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=57945943-2355-447D-9474-89834BADB312@wincent.com \
--to=win@wincent.com \
--cc=git@vger.kernel.org \
--cc=lists@spinlock.ch \
/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