From: Tay Ray Chuan <rctay89@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Jonathan Nieder" <jrnieder@gmail.com>
Subject: [PATCH v3 0/9] http: end urls with slash
Date: Thu, 25 Nov 2010 16:21:01 +0800 [thread overview]
Message-ID: <1290673270-4284-1-git-send-email-rctay89@gmail.com> (raw)
In-Reply-To: <1290433298-6000-1-git-send-email-rctay89@gmail.com>
This patch series contains Gabriel's fix, as well as some related work I did in
the area while looking through the code paths.
Changed from v2:
- new patches (#2 and #9) that reworks http-fetch url slashing code, and test
that this doesn't break anything.
- patch #4: remove pointer check before running free(), as pointed out by
Johnathan.
All other patches remain unchanged.
Contents:
[1/9] t5550-http-fetch: add missing '&&'
[2/9] t5550-http-fetch: add test for http-fetch
[3/9] shift end_url_with_slash() from http.[ch] to url.[ch]
[4/9] url: add str wrapper for end_url_with_slash()
[5/9] http-backend: use end_url_with_slash()
[6/9] http-push: Normalise directory names when pushing to some WebDAV servers
[7/9] http-push: check path length before using it
[8/9] http-push: add trailing slash at arg-parse time, instead of later on
[9/9] http-fetch: rework url handling
Makefile | 2 +-
http-backend.c | 4 +---
http-fetch.c | 16 +++++-----------
http-push.c | 31 ++++++++++++++++---------------
http.c | 8 +-------
http.h | 2 +-
t/t5550-http-fetch.sh | 16 ++++++++++++++--
url.c | 14 ++++++++++++++
url.h | 3 +++
9 files changed, 56 insertions(+), 40 deletions(-)
--
1.7.3.2.495.gc7b3f
next prev parent reply other threads:[~2010-11-25 8:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1290433298-6000-1-git-send-email-rctay89@gmail.com>
[not found] ` <1290433657-4444-1-git-send-email-rctay89@gmail.com>
[not found] ` <1290433657-4444-2-git-send-email-rctay89@gmail.com>
[not found] ` <1290433657-4444-3-git-send-email-rctay89@gmail.com>
[not found] ` <1290433657-4444-4-git-send-email-rctay89@gmail.com>
2010-11-22 17:14 ` [PATCH v2 3/7] url: add str wrapper for end_url_with_slash() Jonathan Nieder
2010-11-22 17:19 ` Tay Ray Chuan
2010-11-25 8:21 ` Tay Ray Chuan [this message]
2010-11-25 8:21 ` [PATCH v3 1/9] t5550-http-fetch: add missing '&&' Tay Ray Chuan
2010-11-25 8:21 ` [PATCH v3 2/9] t5550-http-fetch: add test for http-fetch Tay Ray Chuan
2010-11-25 8:21 ` [PATCH v3 3/9] shift end_url_with_slash() from http.[ch] to url.[ch] Tay Ray Chuan
2010-11-25 8:21 ` [PATCH v3 4/9] url: add str wrapper for end_url_with_slash() Tay Ray Chuan
2010-11-25 8:21 ` [PATCH v3 5/9] http-backend: use end_url_with_slash() Tay Ray Chuan
2010-11-25 8:21 ` [PATCH v3 6/9] http-push: Normalise directory names when pushing to some WebDAV servers Tay Ray Chuan
2010-11-25 8:21 ` [PATCH v3 7/9] http-push: check path length before using it Tay Ray Chuan
2010-11-25 8:21 ` [PATCH v3 8/9] http-push: add trailing slash at arg-parse time, instead of later on Tay Ray Chuan
2010-11-25 8:21 ` [PATCH v3 9/9] http-fetch: rework url handling Tay Ray Chuan
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=1290673270-4284-1-git-send-email-rctay89@gmail.com \
--to=rctay89@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
/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).