git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	 Git Mailing List <git@vger.kernel.org>,
	 msysGit Mailinglist <msysgit@googlegroups.com>,
	 Thomas Braun <thomas.braun@virtuell-zuhause.de>,
	 Pat Thoyts <patthoyts@users.sourceforge.net>
Subject: Re: [PATCH] Do not call built-in aliases from scripts
Date: Fri, 28 Jun 2013 13:43:31 -0700	[thread overview]
Message-ID: <7vr4fmm0ek.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAHGBnuOE6vYzM2bKs2SV1qJVoCOX=t-XWnd_Xbs1JRD+sY4dVQ@mail.gmail.com> (Sebastian Schuberth's message of "Fri, 28 Jun 2013 22:23:14 +0200")

Sebastian Schuberth <sschuberth@gmail.com> writes:

> On Thu, Jun 27, 2013 at 8:52 PM, Johannes Schindelin
> <Johannes.Schindelin@gmx.de> wrote:
>
>>> --- a/git-merge-octopus.sh
>>> +++ b/git-merge-octopus.sh
>>> @@ -97,7 +97,7 @@ do
>>>       if test $? -ne 0
>>>       then
>>>               echo "Simple merge did not work, trying automatic merge."
>>> -             git-merge-index -o git-merge-one-file -a ||
>>> +             git merge-index -o git-merge-one-file -a ||
>>
>> This is a problem. 'git-merge-one-file' cannot be split here AFAICT.
>>
>> Of course, we could teach merge-index to read *two* parameters instead of
>> one when it encounters "git" as the <merge-program>. But that would be as
>> hacky as the whole dashed-form business to begin with.
>
> I agree to all of your comments except this one: I did not split
> 'git-merge-one-file' here ...

I do not think Dscho was pointing out any problem with your patch.

He is merely pointing out that the goal of "No git-foo anywhere on
the filesystem" is an unworkable one, as sometimes you need to give
the path of a specific binary to commands.  It is not limited to the
"-o" option of "git merge-index", but the above is a good example.

And I agree with Dscho that this is not a problem with your patch
per-se.

>>>       echo "Simple merge failed, trying Automatic merge."
>>> -     if git-merge-index -o git-merge-one-file -a
>>> +     if git merge-index -o git-merge-one-file -a
>>
>> As above, with -octopus.
>
> Sorry, I can't follow you here.

The same issue above, that you have to have "git-merge-one-file"
somewhere in your filesystem on $GIT_EXEC_PATH, he pointed out when
he commented on the patch to git-merge-octopus.sh, can be seen here.

-- 
-- 
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.

You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups "msysGit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

  parent reply	other threads:[~2013-06-28 20:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 12:47 [PATCH] Do not call built-in aliases from scripts Sebastian Schuberth
2013-06-27 16:11 ` Junio C Hamano
2013-06-27 16:41   ` Sebastian Schuberth
2013-06-27 17:27     ` Junio C Hamano
2013-06-27 18:02       ` John Szakmeister
2013-06-27 18:05         ` Junio C Hamano
2013-06-27 18:10           ` Junio C Hamano
2013-06-28 20:18             ` Sebastian Schuberth
2013-06-27 18:11           ` John Keeping
2013-06-27 18:52 ` Johannes Schindelin
2013-06-28 20:23   ` Sebastian Schuberth
2013-06-28 20:32     ` Johannes Schindelin
2013-06-28 20:43     ` Junio C Hamano [this message]
2013-06-27 19:57 ` Johannes Sixt

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=7vr4fmm0ek.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=msysgit@googlegroups.com \
    --cc=patthoyts@users.sourceforge.net \
    --cc=sschuberth@gmail.com \
    --cc=thomas.braun@virtuell-zuhause.de \
    /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).