[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bad translation merge
From: |
David Kastrup |
Subject: |
Re: Bad translation merge |
Date: |
Wed, 07 Mar 2012 12:10:18 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.92 (gnu/linux) |
David Kastrup <address@hidden> writes:
> Hi, the recent translation merge apparently made some wrong choices when
> dealing with merge conflicts. Changes in staging have been overwritten
> in the following files:
> And that affects a lot more than just translations. I have removed that
> commit from origin/staging, and we'll have to investigate what
> happened. Francisco, do you remember the commands you used for merging
> translation into staging? I'll try repeating this on my own and see
> whether I can reproduce this.
I can reproduce the problems when merging. It would appear that the
history of the translation branch got messed up at some point of time in
a manner that git can't recognize how to merge properly anymore.
I will try to figure out what happened here. Please don't merge the
translation branch to staging while I try figuring this out.
--
David Kastrup
- Bad translation merge, David Kastrup, 2012/03/07
- Re: Bad translation merge,
David Kastrup <=
- Re: Bad translation merge, David Kastrup, 2012/03/07
- Re: Bad translation merge, David Kastrup, 2012/03/07
- Re: Bad translation merge, Graham Percival, 2012/03/07
- Re: Bad translation merge, David Kastrup, 2012/03/07
- Re: Bad translation merge, Phil Holmes, 2012/03/07
- Re: Bad translation merge, Graham Percival, 2012/03/07
- Re: Bad translation merge, David Kastrup, 2012/03/07
Re: Bad translation merge, Julien Rioux, 2012/03/07