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

Re: [PATCH 0/4] Build in some more things

From
Daniel Barkalow <barkalow@iabervon.org>
Date
Oct 30, 2007, 16:49 UTC
Message-ID
<Pine.LNX.4.64.0710301237490.7357@iabervon.org>
In-Reply-To
<4726DC3D.2030202@viscovery.net>
On Tue, 30 Oct 2007, Johannes Sixt wrote:
Show 19 quoted lines
> Daniel Barkalow schrieb:
> > The main effect of this series is removing the fork/exec from pushing via
> > the git protocol (aside from the later fork/exec in connect.c of course).
> > 
> > It also heads off some tempting transport-related fetch bugs, which I will
> > not introduce in a later patch.
> > 
> > * Miscellaneous const changes and utilities
> >   Adds two small utility functions, and marks a bunch of stuff as const; the
> >   const stuff is to keep builtin-fetch from getting messed up without a
> >   warning, because it wants some lists not to change.
> > 
> > * Build-in peek-remote, using transport infrastructure.
> > * Build-in send-pack, with an API for other programs to call.
> > * Use built-in send-pack.
> 
> I assume this goes on top of current master or db/fetch-pack. The patches have
> some conflicts with js/forkexec (nothing serious, though). Maybe it makes
> sense to rebase on top of that.

Current master. As I said to Junio a moment ago (and forgot to cc you, oops), I think 1/4 should go before js/forkexec, being trivial, and 2/4 should also, since it simply removes duplicate code that js/forkexec updates; I should redo 3/4 after the code settles down, and 4/4 is trivial but depends on 3/4.

	-Daniel
*This .sig left intentionally blank*
Previous: Johannes SixtNext: Junio C Hamano
Message 3 of 5 in “Build in some more things”
  1. 0/4 Build in some more thingsDaniel Barkalow, Oct 30, 2007
  2. Johannes SixtOct 30, 2007
  3. Daniel BarkalowOct 30, 2007
  4. Junio C HamanoOct 30, 2007
  5. Daniel BarkalowOct 30, 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.