[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bzr document unclear. There is no "conflict markers".
From: |
Richard Stallman |
Subject: |
Re: Bzr document unclear. There is no "conflict markers". |
Date: |
Mon, 04 Jan 2010 11:23:34 -0500 |
The quick answer is that the "quickfixes" branch could have diverged
from the trunk, for example because some of the developers changes have
not been accepted (yet) into the trunk.
The concept of "accepted into the trunk" puzzles me. If someone has
write access, he can install his changes into the trunk, right? So if
he has committed all his past changes, there's nothing to merge --
right?
Are you assuming the case of a person who doesn't have write access
on Savannah?
- Bzr document unclear. There is no "conflict markers"., Jan Djärv, 2010/01/03
- Re: Bzr document unclear. There is no "conflict markers"., Bojan Nikolic, 2010/01/03
- Re: Bzr document unclear. There is no "conflict markers"., Richard Stallman, 2010/01/03
- Re: Bzr document unclear. There is no "conflict markers"., Bojan Nikolic, 2010/01/03
- Re: Bzr document unclear. There is no "conflict markers".,
Richard Stallman <=
- Re: Bzr document unclear. There is no "conflict markers"., Stefan Monnier, 2010/01/04
- Re: Bzr document unclear. There is no "conflict markers"., Bojan Nikolic, 2010/01/04
- Re: Bzr document unclear. There is no "conflict markers"., Eli Zaretskii, 2010/01/03
- Re: Bzr document unclear. There is no "conflict markers"., Richard Stallman, 2010/01/04
- Re: Bzr document unclear. There is no "conflict markers"., Eli Zaretskii, 2010/01/04