From: Daniel Barkalow <barkalow@iabervon.org>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Anybody using git-send-pack?
Date: Mon, 23 Apr 2007 13:29:43 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704231321550.28708@iabervon.org> (raw)
In order to make git-push update refs/remotes to reflect the change caused
to the remote (without requiring a fetch after the push), I'm finding it
necessary to mess with the interface between git-push and git-send-pack. I
think the easiest thing would be just to pull send-pack into push, rather
than execing another program (now that git-push is also in C).
The question is whether I should write a builtin-send-pack.c that lets
people call send-pack directly, or get rid of it entirely in favor of
always going though git-push. The only reason I can see to call send-pack
directly is that git-push currently loses "verbose" in calling it, which
should probably just be fixed.
Is cogito still using it, perhaps? Is that still an issue?
-Daniel
*This .sig left intentionally blank*
next reply other threads:[~2007-04-23 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 17:29 Daniel Barkalow [this message]
2007-04-23 18:36 ` Anybody using git-send-pack? Junio C Hamano
2007-04-23 18:38 ` 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.0704231321550.28708@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).