On Tue, 30 Oct 2007, Johannes Sixt wrote: > 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* - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
