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

Re: [PATCH 2/4] receive-pack: make it a builtin

From
Paolo Bonzini <bonzini@gnu.org>
Date
Sep 9, 2008, 09:26 UTC
Message-ID
<48C64138.3020406@gnu.org>
In-Reply-To
<1220948830-3275-3-git-send-email-gitster@pobox.com>
Junio C Hamano wrote:
> It is a good thing to do in general, but more importantly, transport
> routines can only be used by built-ins, which is what I'll be adding next.
So how do I
        receive-pack = /home/bonzinip/bin/git-receive-pack

now? Using libexec or ".../bin/git receive-pack" is fine, I just would like to know it and see it in the release notes. Or maybe git-receive-pack should be installed in $(bindir) even if it is a builtin?

Paolo
Previous: Jeff KingNext: Junio C Hamano
Message 7 of 12 in “Pushing into a repository with alternates”
  1. 0/4 Pushing into a repository with alternatesJunio C Hamano, Sep 9, 2008
  2. 1/4 is_directory(): a generic helper functionJunio C Hamano, Sep 9, 2008
  3. 2/4 receive-pack: make it a builtinJunio C Hamano, Sep 9, 2008
  4. 3/4 push: prepare sender to receive extended ref information from the receiverJunio C Hamano, Sep 9, 2008
  5. 4/4 push: receiver end advertises refs from alternate repositoriesJunio C Hamano, Sep 9, 2008
  6. Jeff KingSep 9, 2008
  7. Paolo BonziniSep 9, 2008
  8. Junio C HamanoSep 9, 2008
  9. Paolo BonziniSep 9, 2008
  10. Johannes SixtSep 9, 2008
  11. Jeff KingSep 9, 2008
  12. Junio C HamanoSep 9, 2008

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.