From: Jay Soffian <jaysoffian@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 0/5] Extend pattern refspecs
Date: Fri, 6 Mar 2009 01:52:49 -0500 [thread overview]
Message-ID: <76718490903052252y1778aa41g8f3e52329f7bf288@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0903060038510.19665@iabervon.org>
On Fri, Mar 6, 2009 at 1:07 AM, Daniel Barkalow <barkalow@iabervon.org> wrote:
> On Fri, 6 Mar 2009, Jay Soffian wrote:
>
> Actually, you should be able to just drop your "buf" and use spec->src and
> spec->dst, since it just stores the original strings. So that should be
> easy enough, although it might be good to go through a remote.c function
> just in case it becomes more complicated later. On the other hand,
> get_head_names() should probably get a patch like my 1/5 to have it use
> the remote.c parser, or should use a constant "head mirror" refspec like
> that tag_refspec already in remote.c
Okay.
> Do you have tests for "git remote show -n"?
Yes. Apparently not enough of them though if nothing is failing.
> Merging my series (on top of
> origin/master) and e5dcbfd and adding a final '*' to the string in
> get_head_names() made everything pass for me, without doing anything about
> the extra *s, but the output is clearly not quite right.
Hmm, alright.
> I'm not seeing anything that makes assumptions about the matching
> semantics of pattern refspecs, just stuff about how the stored form
> relates to the config-file form.
Okay, that sounds right.
I assume your series will end up in pu soon enough, and I think my
series is about to hop to next. What's the right way to to have them
be happy together?
j.
next prev parent reply other threads:[~2009-03-06 6:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 4:56 [PATCH 0/5] Extend pattern refspecs Daniel Barkalow
2009-03-06 5:19 ` Jay Soffian
2009-03-06 6:07 ` Daniel Barkalow
2009-03-06 6:52 ` Jay Soffian [this message]
2009-03-06 7:03 ` Daniel Barkalow
2009-03-06 7:59 ` Jay Soffian
2009-03-08 8:31 ` Junio C Hamano
2009-03-08 8:49 ` Daniel Barkalow
2009-03-09 15:46 ` Jay Soffian
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=76718490903052252y1778aa41g8f3e52329f7bf288@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).