mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Ilya Kantor <>
Subject: [git for translators] How to always generate conflicts for merges?
Date: Thu, 25 Jul 2019 16:42:48 +0300	[thread overview]
Message-ID: <> (raw)


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 a new file is added to English, it just gets auto-merged into Japanese.
But all new changes must be human-controlled, translated. 

Is there a way to force git always generate a conflict, even if changes could be auto-merged?


             reply	other threads:[~2019-07-25 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-25 13:42 Ilya Kantor [this message]
2019-07-25 14:25 ` [git for translators] How to always generate conflicts for merges? Santiago Torres Arias
2019-07-25 16:37 ` Junio C Hamano
2019-07-25 17:42   ` Ilya Kantor
2019-07-26 20:40     ` Sergey Lukashev

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).