From: Junio C Hamano <gitster@pobox.com>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Johannes Sixt <johannes.sixt@telecom.at>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 0/7] prefix discovery at runtime (on Windows)
Date: Sun, 17 Aug 2008 11:01:25 -0700 [thread overview]
Message-ID: <7v3al35xmy.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1218977083-14526-1-git-send-email-prohaska@zib.de> (Steffen Prohaska's message of "Sun, 17 Aug 2008 14:44:36 +0200")
Steffen Prohaska <prohaska@zib.de> writes:
> Apologies for proposing such large changes that late in the release cycle.
> Maybe we want to postpone the series until 1.6.0.1 or even 1.6.1.
Well, from the cursory look, it does not seem to be 1.6.0.1 material, even
though it is possible to fork a topic at 1.6.0 and use the changes in
'next', then 'master', and eventually to 'maint' to produce 1.6.0.X, if
all of this hapapens before 1.6.1.
I wouldn't mind at all if the binary distribution on Windows is based on
"git.git plus port specific patchset that will eventually be sent
upstream" like it used to be. In fact it might even be preferrable, as I
won't be testing ports to that platform myself anyway.
next prev parent reply other threads:[~2008-08-17 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-17 12:44 [PATCH 0/7] prefix discovery at runtime (on Windows) Steffen Prohaska
2008-08-17 12:44 ` [PATCH 1/7] Windows: Add workaround for MSYS' path conversion Steffen Prohaska
2008-08-17 12:44 ` [PATCH 2/7] system_path(): Add prefix computation at runtime if RUNTIME_PREFIX set Steffen Prohaska
2008-08-17 12:44 ` [PATCH 3/7] Refactor git_set_argv0_path() to git_extract_argv0_path() Steffen Prohaska
2008-08-17 12:44 ` [PATCH 4/7] Glean libexec path from argv[0] for git-upload-pack and git-receive-pack Steffen Prohaska
2008-08-17 12:44 ` [PATCH 5/7] Add calls to git_extract_argv0_path() in programs that call git_config_* Steffen Prohaska
2008-08-17 12:44 ` [PATCH 6/7] Modify setup_path() to only add git_exec_path() to PATH Steffen Prohaska
2008-08-17 12:44 ` [PATCH 7/7] Windows: Revert to default paths and convert them by RUNTIME_PREFIX Steffen Prohaska
2008-08-17 20:28 ` [PATCH 6/7] Modify setup_path() to only add git_exec_path() to PATH Johannes Sixt
2008-08-17 20:43 ` [PATCH 2/7] system_path(): Add prefix computation at runtime if RUNTIME_PREFIX set Johannes Sixt
2008-08-18 5:28 ` Steffen Prohaska
2008-08-17 20:35 ` [PATCH 1/7] Windows: Add workaround for MSYS' path conversion Johannes Sixt
2008-09-21 7:48 ` Steffen Prohaska
2008-08-17 18:01 ` Junio C Hamano [this message]
2008-09-08 22:50 ` [PATCH 0/7] prefix discovery at runtime (on Windows) Junio C Hamano
2008-09-09 14:49 ` Johannes Schindelin
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=7v3al35xmy.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=johannes.sixt@telecom.at \
--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).