[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Stupid git!
From: |
Stephen J. Turnbull |
Subject: |
Re: Stupid git! |
Date: |
Tue, 15 Sep 2015 09:24:19 +0900 |
Alan Mackenzie writes:
> Yes. I had misunderstood "conflict". I had thought it meant a merge
> conflict in some file, whereas it just meant that other, possibly
> unrelated, changes had taken place.
No, "conflict" means that there are conflicts in a file so that the
expected outcome of the merge is indeterminate, just like every other
VCS. There could be a bug in git's implementation, but this
terminology is standard in git as in other VCSes.
- Re: Stupid git!, (continued)
- Re: Stupid git!, David Kastrup, 2015/09/14
- Re: Stupid git!, Eli Zaretskii, 2015/09/14
- Re: Stupid git!, David Kastrup, 2015/09/14
- Re: Stupid git!, Eli Zaretskii, 2015/09/14
- Re: Stupid git!, David Kastrup, 2015/09/14
- Re: Stupid git!, Eli Zaretskii, 2015/09/14
- Re: Stupid git!, David Kastrup, 2015/09/14
- Re: Stupid git!, Stefan Monnier, 2015/09/14
- Re: Stupid git!, Eli Zaretskii, 2015/09/13
- Re: Stupid git!, Alan Mackenzie, 2015/09/14
- Re: Stupid git!,
Stephen J. Turnbull <=
- Re: Stupid git!, Dmitry Gutov, 2015/09/13
- Re: Stupid git!, Stephen J. Turnbull, 2015/09/13
- Re: Stupid git!, Dmitry Gutov, 2015/09/14
- Re: Stupid git!, Alan Mackenzie, 2015/09/14
- Re: Stupid git!, Eli Zaretskii, 2015/09/14
- Re: Stupid git!, Dmitry Gutov, 2015/09/14
- Re: Stupid git!, Steinar Bang, 2015/09/14
- Re: Stupid git!, Steinar Bang, 2015/09/14
- Re: Stupid git!, Eli Zaretskii, 2015/09/13