From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: What's in master tonight.
Date: Sun, 20 Nov 2005 00:40:21 -0800 [thread overview]
Message-ID: <7v7jb31zm2.fsf@assigned-by-dhcp.cox.net> (raw)
I've merged http updates (mostly code refactoring and cleanups)
from Nick Hengeveld, config-set from Johannes Schindelin, and
most of user-relative paths series from Andreas Ericsson.
Cooking in proposed updates are the final part of user-relative
paths series that changes git-daemon, git:// proxy support from
Paul Collins, and repository format futureproofing from Martin
Atukunda.
I'd like to do the next 1.0rc when at least the repository
format futureproofing is ready. I personally can live without
user-relative paths or git:// proxy, although both are probably
nice to have. Here are the current status of these three
topics.
repository format futureproofing::
I think the current code can copy template/config that
was prepared for wrong version of repository format
without complaining. It should barf and fail.
I am unsure if the check in setup_git_repository() is
the right thing to do. It doesn't check when $GIT_DIR
environment is set, which is wrong; receive-pack and
upload-pack are run with this environment set to ".".
Although majority of important core programs do check
the repository format before doing any harmful
operations, some higher level scripts should be told to
do the checking upfront. The config-set command by
Johannes is probably handy for this purpose.
user relative paths::
What's left from the master is the part that touches the
git-daemon. We need to be careful about being strict
while validating the path against whitelist _after_
DWIM, so the version in the proposed updates need to be
checked to make sure it is safe.
proxy for git:// transport:
I do not have any pending issues on this patch, and I
think it is ready to go in when somebody, preferably
other than the original author, says it is useful and
does not break things.
The master branch is fairly ahead of the last 1.0rc as of this
writing, and I'll be attending a wedding of a coworker, so there
will not be maint updates this weekend.
next reply other threads:[~2005-11-20 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 8:40 Junio C Hamano [this message]
2005-11-20 14:28 ` Simple proxy test (was Re: What's in master tonight) Yaacov Akiba Slama
-- strict thread matches above, loose matches on Subject: below --
2005-12-11 8:06 What's in master tonight 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=7v7jb31zm2.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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 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).