From: Junio C Hamano <junkio@cox.net>
To: git@vger.kernel.org
Subject: Re: [RFC] get_pathspec(): free() old buffer if rewriting
Date: Sat, 06 May 2006 21:50:45 -0700 [thread overview]
Message-ID: <7vejz6phei.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7viroipijf.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Sat, 06 May 2006 21:26:12 -0700")
Junio C Hamano <junkio@cox.net> writes:
> int match_pathspec(const char *path, int len,
> struct pathspec **pathspec);
>
> See if the path (with length) matches the given spec.
> path[len-1] == '/' signals that the caller is traversing
> a tree and checking if it is worth descending into the
> tree.
> ...
> and when traversing the tree for A and B, upon seeing "Documentation"
> entry in the topleve tree object buffers, call:
>
> path_match("Documentation", 14, 1, spec)
Oops, match_pathspec("Documentation/", 15, spec) is what I meant
here. Likewise in the later examples.
prev parent reply other threads:[~2006-05-07 4:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 22:04 [RFC] get_pathspec(): free() old buffer if rewriting Johannes Schindelin
2006-05-06 22:37 ` Linus Torvalds
2006-05-06 22:44 ` Johannes Schindelin
2006-05-07 4:26 ` Junio C Hamano
2006-05-07 4:50 ` 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=7vejz6phei.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).