git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j6t@kdbg.org>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 1/6] Move computation of absolute paths from Makefile to runtime and compute prefix on the fly if RUNTIME_PREFIX set
Date: Tue, 13 Jan 2009 20:43:16 +0100	[thread overview]
Message-ID: <200901132043.16789.j6t@kdbg.org> (raw)
In-Reply-To: <1231595452-27698-1-git-send-email-prohaska@zib.de>

On Samstag, 10. Januar 2009, Steffen Prohaska wrote:
> This is the first commit of a series that adds support for
> relocatable binaries (called RUNTIME_PREFIX).  Such binaries can be
> moved together with the system configuration files to a different
> directory, as long as the relative paths from the binary to the
> configuration files is preserved.  This functionality is essential
> on Windows where we deliver git binaries with an installer that
> allows to freely choose the installation location.  The commit
> series implements RUNTIME_PREFIX only on Windows.  Adding support
> on Unix should not be too hard, though.

This series looks sane, and my comments on 2/6 and 3/6 certainly do not 
indicate any showstoppers. I've just started using it; so far there are no 
problems.

-- Hannes

      parent reply	other threads:[~2009-01-13 19:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-10 13:50 [PATCH 1/6] Move computation of absolute paths from Makefile to runtime and compute prefix on the fly if RUNTIME_PREFIX set Steffen Prohaska
2009-01-10 13:50 ` [PATCH 2/6] Refactor git_set_argv0_path() to git_extract_argv0_path() Steffen Prohaska
2009-01-10 13:50   ` [PATCH 3/6] Glean libexec path from argv[0] for git-upload-pack and git-receive-pack Steffen Prohaska
2009-01-10 13:50     ` [PATCH 4/6] Add calls to git_extract_argv0_path() in programs that call git_config_* Steffen Prohaska
2009-01-10 13:50       ` [PATCH 5/6] Modify setup_path() to only add git_exec_path() to PATH Steffen Prohaska
2009-01-10 13:50         ` [PATCH 6/6] Windows: Revert to default paths and convert them by RUNTIME_PREFIX Steffen Prohaska
2009-01-10 14:34     ` [PATCH 3/6] Glean libexec path from argv[0] for git-upload-pack and git-receive-pack Johannes Schindelin
2009-01-10 15:55       ` Steffen Prohaska
2009-01-10 16:01       ` Steffen Prohaska
2009-01-10 20:36         ` Junio C Hamano
2009-01-11 10:04           ` Steffen Prohaska
2009-01-11 10:21             ` Junio C Hamano
2009-01-11 12:57               ` Steffen Prohaska
2009-01-13 19:36     ` Johannes Sixt
2009-01-13 19:37   ` [PATCH 2/6] Refactor git_set_argv0_path() to git_extract_argv0_path() Johannes Sixt
2009-01-13 19:43 ` Johannes Sixt [this message]

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=200901132043.16789.j6t@kdbg.org \
    --to=j6t@kdbg.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=prohaska@zib.de \
    /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).