git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: mhagger@alum.mit.edu, git@vger.kernel.org,
	Jeff King <peff@peff.net>, Drew Northup <drew.northup@maine.edu>,
	Jakub Narebski <jnareb@gmail.com>,
	Heiko Voigt <hvoigt@hvoigt.net>,
	Johan Herland <johan@herland.net>,
	Julian Phillips <julian@quantumfyre.co.uk>
Subject: Re: [PATCH] t1402-check-ref-format: skip tests of refs beginning with slash on Windows
Date: Fri, 14 Oct 2011 08:40:53 +0200	[thread overview]
Message-ID: <4E97D975.6070305@viscovery.net> (raw)
In-Reply-To: <7vbotk32zm.fsf@alter.siamese.dyndns.org>

Am 10/14/2011 1:07, schrieb Junio C Hamano:
> Junio C Hamano <gitster@pobox.com> writes:
> 
>>> +invalid_ref NOT_MINGW '/'
>>> ...
>>> +valid_ref_normalized '/heads/foo' 'heads/foo' NOT_MINGW
>>
>> The inconsistencies strikes me a bit.
> 
> Here is what I tentatively will queue.

The patch looks good, and the test cases pass as expected.

Thank you very much,
-- Hannes

      reply	other threads:[~2011-10-14  6:41 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-13  7:58 [PATCH 00/14] Tidying up references code mhagger
2011-10-13  7:58 ` [PATCH 01/14] cache.h: add comments for git_path() and git_path_submodule() mhagger
2011-10-13 18:37   ` Junio C Hamano
2011-10-13  7:58 ` [PATCH 02/14] struct ref_list: document name member mhagger
2011-10-13 18:37   ` Junio C Hamano
2011-10-13  7:58 ` [PATCH 03/14] refs.c: rename some local "refname" variables mhagger
2011-10-13  7:58 ` [PATCH 04/14] refs: rename some parameters result -> sha1 mhagger
2011-10-13 18:42   ` Junio C Hamano
2011-10-13  7:58 ` [PATCH 05/14] clear_ref_list(): rename from free_ref_list() mhagger
2011-10-13 18:43   ` Junio C Hamano
2011-10-13  7:58 ` [PATCH 06/14] resolve_gitlink_ref(): improve docstring mhagger
2011-10-13 18:48   ` Junio C Hamano
2011-10-13  7:58 ` [PATCH 07/14] is_refname_available(): remove the "quiet" argument mhagger
2011-10-13 12:41   ` Drew Northup
2011-10-13 18:49     ` Junio C Hamano
2011-10-14  5:35     ` Michael Haggerty
2011-10-13  7:58 ` [PATCH 08/14] parse_ref_line(): add docstring mhagger
2011-10-13  7:58 ` [PATCH 09/14] add_ref(): " mhagger
2011-10-13  7:58 ` [PATCH 10/14] is_dup_ref(): extract function from sort_ref_list() mhagger
2011-10-13 20:43   ` Junio C Hamano
2011-10-13  7:58 ` [PATCH 11/14] refs: change signatures of get_packed_refs() and get_loose_refs() mhagger
2011-10-13  7:58 ` [PATCH 12/14] get_ref_dir(): change signature mhagger
2011-10-13  7:58 ` [PATCH 13/14] Pass a (cached_refs *) to the resolve_gitlink_*() functions mhagger
2011-10-13  7:58 ` [PATCH 14/14] resolve_gitlink_ref_recursive(): change to work with struct cached_refs mhagger
2011-10-13  8:06 ` [PATCH] t1402-check-ref-format: skip tests of refs beginning with slash on Windows Johannes Sixt
2011-10-13 23:00   ` Junio C Hamano
2011-10-13 23:07     ` Junio C Hamano
2011-10-14  6:40       ` 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=4E97D975.6070305@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=drew.northup@maine.edu \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hvoigt@hvoigt.net \
    --cc=jnareb@gmail.com \
    --cc=johan@herland.net \
    --cc=julian@quantumfyre.co.uk \
    --cc=mhagger@alum.mit.edu \
    --cc=peff@peff.net \
    /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).