From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Git Mailing List <git@vger.kernel.org>,
Steffen Prohaska <prohaska@zib.de>
Subject: Re: What's cooking in git.git (Jan 2009, #06; Sat, 24)
Date: Mon, 26 Jan 2009 09:47:02 -0800 [thread overview]
Message-ID: <7vy6wy6ju1.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 497D6BA7.4070409@viscovery.net
Johannes Sixt <j.sixt@viscovery.net> writes:
> Junio C Hamano schrieb:
>> * sp/runtime-prefix (Sun Jan 18 13:00:15 2009 +0100) 7 commits
>> - Windows: Revert to default paths and convert them by
>> RUNTIME_PREFIX
>> - Compute prefix at runtime if RUNTIME_PREFIX is set
>> - Modify setup_path() to only add git_exec_path() to PATH
>> - Add calls to git_extract_argv0_path() in programs that call
>> git_config_*
>> - git_extract_argv0_path(): Move check for valid argv0 from caller
>> to callee
>> - Refactor git_set_argv0_path() to git_extract_argv0_path()
>> - Move computation of absolute paths from Makefile to runtime (in
>> preparation for RUNTIME_PREFIX)
>>
>> We should move this to 'next' soon with J6t's blessing.
>
> I've been using this series for a few days now without problems:
>
> Acked-by: Johannes Sixt <j6t@kdbg.org>
Thanks. I take that as not just "have been using this and no breakage
observed" but also "of course the patches themselves make sense to me".
prev parent reply other threads:[~2009-01-26 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 5:00 What's cooking in git.git (Jan 2009, #06; Sat, 24) Junio C Hamano
2009-01-25 12:17 ` Johannes Schindelin
2009-01-25 18:51 ` Jeff King
2009-01-26 7:52 ` Johannes Sixt
2009-01-26 17:47 ` Junio C Hamano [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=7vy6wy6ju1.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--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).