git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to pull remote branch with specified commit id?

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Jan 14, 2009, 07:01 UTC
Message-ID
<496D8DC4.1060904@viscovery.net>
In-Reply-To
<496D0E65.3000200@kitware.com>
Brad King schrieb:
Show 10 quoted lines
> 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?
No, assuming that-branch was the only ref that contained the objects.

Even if the repack happens before the branch is deleted, the objects that were *only* in that-branch will not be sent out.

-- Hannes
Previous: Johannes Sixt
Message 8 of 8 in “How to pull remote branch with specified commit id?”
  1. Emily RenJan 13, 2009
  2. Andreas EricssonJan 13, 2009
  3. Emily RenJan 13, 2009
  4. Johannes SixtJan 13, 2009
  5. Brad KingJan 13, 2009
  6. thestar@fussycoder.id.auJan 14, 2009
  7. Johannes SixtJan 14, 2009
  8. Johannes SixtJan 14, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.