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

Re: Pushing and fetching sha1s directly

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Dec 23, 2007, 20:04 UTC
Message-ID
<Pine.LNX.4.64.0712232003470.23902@racer.site>
In-Reply-To
<7vlk7mwchm.fsf@gitster.siamese.dyndns.org>
Hi,
On Sat, 22 Dec 2007, Junio C Hamano wrote:
Show 10 quoted lines
> Finn Arne Gangstad <finnag@pvv.org> writes:
> 
> > Currently there seems to be no way of pusing a sha1 directly, or to 
> > fetch a sha1 directly. When working with submodules, it is convenient 
> > to be able to work with detached HEADs, so it would be good if this 
> > could be supported also by fetch and push.
> 
> For fetch, I would normally say "check the list archives", but it was 
> very long time ago that it was proposed and discussed. It has some 
> security and performance implications.

To enhance on that: sometimes you need to delete a branch in a hurry, because you publicised some secret code/file. In that case, you do _not_ want people being able to fetch arbitrary commits.

Ciao, Dscho

Previous: Junio C Hamano
Message 3 of 3 in “Pushing and fetching sha1s directly”
  1. Finn Arne GangstadDec 22, 2007
  2. Junio C HamanoDec 22, 2007
  3. Johannes SchindelinDec 23, 2007

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.