From: Jay Soffian <jaysoffian@gmail.com>
To: Daniel Barkalow <barkalow@iabervon.org>,
Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 0/5] Extend pattern refspecs
Date: Mon, 9 Mar 2009 11:46:25 -0400 [thread overview]
Message-ID: <76718490903090846x2e84816emed5e21da9788680d@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0903080447450.19665@iabervon.org>
On Sun, Mar 8, 2009 at 4:49 AM, Daniel Barkalow <barkalow@iabervon.org> wrote:
> On Sun, 8 Mar 2009, Junio C Hamano wrote:
>
>> Jay Soffian <jaysoffian@gmail.com> writes:
>>
>> > This series and js/remote-improvements (e5dcbfd) in pu may not get
>> > along completely. "git remote show" tries to show how the refspecs
>> > expand out.
>>
>> I've created an "early semantic conflict resolution" topic branch that is
>> a cross between this series and js/remote-improvements, like so:
>>
>> $ git checkout -b xx/db-refspec-vs-js-remote db/refspec-wildcard-in-the-middle
>> $ git merge js/remote-improvements
>> $ git apply evil-fixup.diff
>> $ git commit --amend -a -m "Evil merge."
>>
>> with the following "fixup-as-an-evil-merge patch", which I'd appreciate if
>> you two can sanity check.
>
> That looks like what I'd come up with as a resolution, too, so I think
> it's sane unless Jay knows of another way to get remote to care about
> patterns.
Looks good to me too.
j.
prev parent reply other threads:[~2009-03-09 15:47 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
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 [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=76718490903090846x2e84816emed5e21da9788680d@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).