From: Brad King <brad.king@kitware.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Git Mailinglist <git@vger.kernel.org>
Subject: Re: How to pull remote branch with specified commit id?
Date: Tue, 13 Jan 2009 16:57:57 -0500 [thread overview]
Message-ID: <496D0E65.3000200@kitware.com> (raw)
In-Reply-To: <496C6234.9040903@viscovery.net>
Johannes Sixt wrote:
> Consider this: You accidentally push a branch with confidential data to a
> public repository. You notice it early, and quickly delete the branch
> using 'git push the-repo :refs/heads/that-branch'. At this time the
> objects with the confidential data are still lingering in the public
> repository. But with the current behavior noone can access them even if
> the SHA1 happens to be known.
Might a repack (perhaps an automatic one) put the object in a pack
(perhaps in a delta chain) that can be fetched through another ref?
-Brad
next prev parent reply other threads:[~2009-01-13 22:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 9:08 How to pull remote branch with specified commit id? Emily Ren
2009-01-13 9:16 ` Andreas Ericsson
2009-01-13 13:15 ` Emily Ren
2009-01-13 9:43 ` Johannes Sixt
2009-01-13 21:57 ` Brad King [this message]
2009-01-14 5:54 ` thestar
2009-01-14 7:02 ` Johannes Sixt
2009-01-14 7:01 ` Johannes Sixt
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=496D0E65.3000200@kitware.com \
--to=brad.king@kitware.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).