From: Junio C Hamano <junkio@cox.net>
To: Bill Lear <rael@zopyra.com>
Cc: git@vger.kernel.org
Subject: Re: Support for config wildcards
Date: Tue, 13 Mar 2007 12:50:26 -0700 [thread overview]
Message-ID: <7v8xe0j531.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <17910.59652.481204.872797@lisa.zopyra.com> (Bill Lear's message of "Tue, 13 Mar 2007 12:10:12 -0600")
Bill Lear <rael@zopyra.com> writes:
> But that doesn't work for your example "all but xyz". I guess in that
> case, I would need to check both branch patterns and if one did not
> match, then I would reject it and not add to the recipient list.
>
> Was that basically what you had in mind?
Yes, similar to how positive and negative entries in .gitignore
influences the final outcome of the 'ignoredness' for each path.
prev parent reply other threads:[~2007-03-13 19:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 16:47 Support for config wildcards Bill Lear
2007-03-13 17:03 ` Junio C Hamano
2007-03-13 18:10 ` Bill Lear
2007-03-13 19: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=7v8xe0j531.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=rael@zopyra.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).