From: Paolo Bonzini <bonzini@gnu.org>
To: git@vger.kernel.org
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/4] receive-pack: make it a builtin
Date: Tue, 09 Sep 2008 16:47:55 +0200 [thread overview]
Message-ID: <48C68C9B.8070402@gnu.org> (raw)
In-Reply-To: <7v63p59z3w.fsf@gitster.siamese.dyndns.org>
>> 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.
>
> Please check your Makefile (I'm too lazy to double check); don't we
> install these server side programs in $(bindir)?
Yes, I interpreted the obsolete comment in Makefile
# ... and all the rest that could be moved out of bindir to gitexecdir
as s/could be/were/, but there is a special rule in install to place
these in $(bindir).
Paolo
next prev parent reply other threads:[~2008-09-09 14:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 8:27 [PATCH 0/4] Pushing into a repository with alternates Junio C Hamano
2008-09-09 8:27 ` [PATCH 1/4] is_directory(): a generic helper function Junio C Hamano
2008-09-09 8:27 ` [PATCH 2/4] receive-pack: make it a builtin Junio C Hamano
2008-09-09 8:27 ` [PATCH 3/4] push: prepare sender to receive extended ref information from the receiver Junio C Hamano
2008-09-09 8:27 ` [PATCH 4/4] push: receiver end advertises refs from alternate repositories Junio C Hamano
2008-09-09 13:03 ` [PATCH 3/4] push: prepare sender to receive extended ref information from the receiver Jeff King
2008-09-09 9:26 ` [PATCH 2/4] receive-pack: make it a builtin Paolo Bonzini
2008-09-09 14:24 ` Junio C Hamano
2008-09-09 14:47 ` Paolo Bonzini [this message]
2008-09-09 10:31 ` [PATCH 1/4] is_directory(): a generic helper function Johannes Sixt
2008-09-09 12:32 ` Jeff King
2008-09-09 14:51 ` Junio C Hamano
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=48C68C9B.8070402@gnu.org \
--to=bonzini@gnu.org \
--cc=git@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.