From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH 0/4] Build in some more things
Date: Mon, 29 Oct 2007 21:05:35 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0710292049450.7357@iabervon.org> (raw)
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.
Makefile | 4 ++-
builtin-fetch.c | 10 +++---
peek-remote.c => builtin-peek-remote.c | 55 +++++++++++++---------------
send-pack.c => builtin-send-pack.c | 46 ++++++++++++++++--------
builtin.h | 2 +
cache.h | 2 +-
connect.c | 10 +++++-
git.c | 2 +
http-push.c | 2 +-
remote.c | 32 +++++++++++-----
remote.h | 10 ++++--
send-pack.h | 18 +++++++++
transport.c | 63 +++++++++-----------------------
transport.h | 6 ++--
14 files changed, 146 insertions(+), 116 deletions(-)
-Daniel
*This .sig left intentionally blank*
next reply other threads:[~2007-10-30 1:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 1:05 Daniel Barkalow [this message]
2007-10-30 7:24 ` [PATCH 0/4] Build in some more things Johannes Sixt
2007-10-30 16:49 ` Daniel Barkalow
2007-10-30 8:14 ` Junio C Hamano
2007-10-30 16:37 ` Daniel Barkalow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0710292049450.7357@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).