From: Caleb Cushing <xenoterracide@gmail.com>
To: markus.heidelberg@web.de
Cc: git@vger.kernel.org
Subject: Re: [PATCH] mergetool merge/skip/abort
Date: Thu, 22 Jan 2009 00:07:27 -0500 [thread overview]
Message-ID: <81bfc67a0901212107i466335b3h863745902fb688c@mail.gmail.com> (raw)
In-Reply-To: <200901211949.53432.markus.heidelberg@web.de>
> This looks to me like no merge will happen if --no-prompt/-y or
> mergetool.prompt is set to false. Have you tested with this option or
> have I misread?
sorry haven't tested as I don't use that. will test in the morning...
if it doesn't work will try to get it working.
> Also, I think you've lost some tabs. Mergetool does have some
> inconsistent tabbing but they way I've been aiming towards (which
> matches most, but not all of git-mergetool.sh) is to use tabs == 8
> spaces for indents but to indent each level by 4 spaces. e.g. three
> levels of indent is one tab plus four spaces.
thanks wasn't sure on the indentation, I set tabstop to 4 spaces in
vim so my tabs look like your spaces. I'll correct in the next case.
> It might be quite nice to offer the option of directly using an 'ours'
> or 'theirs' as an alternative to skip for binary files. A bit like
> symlinks are handled in mergetool.
I could look into it... at the same time I don't have a good test case
so I'd rather leave it to someone else.
> I'd like to keep (additionally) the behaviour, that the merge starts
> with just pressing <Enter>. Because what you mostly want to do, when
> using git-mergetool, is actually merging.
I'd thought of that... and I'll see what I can do, although to me it
doesn't matter much.
> This doesn't seem right.
erm.. yeah... I'll fix it
--
Caleb Cushing
http://xenoterracide.blogspot.com
next prev parent reply other threads:[~2009-01-22 5:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 14:37 [PATCH] mergetool merge/skip/abort Caleb Cushing
2009-01-21 16:17 ` Caleb Cushing
2009-01-21 16:33 ` Johannes Schindelin
2009-01-21 18:49 ` Markus Heidelberg
2009-01-22 5:07 ` Caleb Cushing [this message]
2009-01-21 17:04 ` Charles Bailey
2009-01-22 14:17 ` Caleb Cushing
2009-01-22 14:22 ` Charles Bailey
2009-01-23 15:16 ` Caleb Cushing
2009-01-23 17:26 ` Junio C Hamano
2009-01-24 18:36 ` Caleb Cushing
2009-01-24 21:45 ` Nanako Shiraishi
2009-01-25 0:18 ` Caleb Cushing
2009-01-25 5:20 ` Junio C Hamano
2009-01-26 22:58 ` Theodore Tso
2009-01-27 22:09 ` Charles Bailey
2009-01-27 22:37 ` Junio C Hamano
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=81bfc67a0901212107i466335b3h863745902fb688c@mail.gmail.com \
--to=xenoterracide@gmail.com \
--cc=git@vger.kernel.org \
--cc=markus.heidelberg@web.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).