Re: [git for translators] How to always generate conflicts for merges?

2019-07-25 Thread Ilya Kantor
xactly in the places where English version changed. Sometimes though, e.g. when a new chapter is added to upstream, the merge just goes through "successfully". That's what I'd like to avoid, as all changes need to be human-controlled. --- Ilya Kantor https://javascript.info &g

[git for translators] How to always generate conflicts for merges?

2019-07-25 Thread Ilya Kantor
Hi, We're using Git to manage translations of an open-source book, and most of time it works well. But there's also a problem. When we pull changes from upstream (English) to translation (e.g. Japanese), git auto-merges them. Sometimes there conflicts, but not all the time. For example, when

Re: Is rebase --force-rebase any different from rebase --no-ff?

2018-05-10 Thread Ilya Kantor
Hi, If that's indeed true (as far as I could see that, still can be mistaken), then as a git user, not developer, I'd stick to --no-ff, because it's the more intuitive naming. Just 5ยข. --- Best Regards, Ilya Kantor On Thu, May 10, 2018 at 9:34 PM, Marc Branchaud wrote: > O

Re: Is rebase --force-rebase any different from rebase --no-ff?

2018-05-09 Thread Ilya Kantor
se --force-rebase -i 54a4 git rebase --no-ff -i 54a4 (picks all 3 commits of feature) Is there a case where --no-ff differs from --force-rebase? --- Best Regards, Ilya Kantor On Wed, May 9, 2018 at 10:27 PM, Marc Branchaud wrote: > On 2018-05-09 02:21 PM, Stefan Beller wrote: >> >&

Is rebase --force-rebase any different from rebase --no-ff?

2018-05-09 Thread Ilya Kantor
l. Probably, there was a difference some time ago, but not now? Then one of them can be safely deprecated. --- Best Regards, Ilya Kantor

Re: cherry-pick --no-commit does not work well with --continue in case of conflicts

2018-05-05 Thread Ilya Kantor
Let's say master..feature has 2 commits: A and B. Then `git cherry-pick -n master..feature` should pick-up A and then B into the working directory and the index. If applying A leads to a conflict, then it stops on A, like here: >>> git cherry-pick -n master..feature >> error: could not apply 2c11

cherry-pick --no-commit does not work well with --continue in case of conflicts

2018-05-05 Thread Ilya Kantor
check that prevents --continue and should be fixed? --- Best Regards, Ilya Kantor

After a rebase, ORIG_HEAD points to the previous tip of the branch?

2018-04-08 Thread Ilya Kantor
. Not sure if it's a bug or not. --- Best Regards, Ilya Kantor

git rerere to remember half-merged progress - valid use?

2018-03-10 Thread Ilya Kantor
ck? I couldn't find such use of rerere in the internet. How can I save the merge/restore progress otherwise? --- Best Regards, Ilya Kantor

Re: Why gc --auto is called so rarely?

2017-11-19 Thread Ilya Kantor
...It seems sane to git gc --auto from command that are expected to take time. That's probably the reason why it's not called on commits and called on receive-pack. But then why call it on merges? Especially on those that have no conflicts and should run fast. Also, merges are not supposed to

Why gc --auto is called so rarely?

2017-11-19 Thread Ilya Kantor
ments? Why there? In particular, gc --auto was called in commits earlier, but not in the recent versions of git. --- Best Regards, Ilya Kantor

What's the idea of specifying binary=true together with textconv?

2017-09-27 Thread Ilya Kantor
ary = true together with textconv? There is an example in docs: [diff "ps"] textconv = ps2ascii binary = true ...But what binary = true does here? Even if we remove it, textconv is called for all ps-files. --- Best Regards, Ilya Kantor

[PATCH] userdiff: fix HTML hunk header regexp

2017-09-23 Thread Ilya Kantor
Current HTML header regexp doesn't match headers without attributes. So it fails to match ..., while ... matches. The fix makes attributes optional. The regexp is still far from perfect, but now it at least handles the common case. Signed-off-by: Ilya Kantor --- userdiff.c | 2 +- 1