[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Confusing "bzr log" as result of merges
From: |
Andreas Schwab |
Subject: |
Re: Confusing "bzr log" as result of merges |
Date: |
Sat, 21 May 2011 10:36:57 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux) |
Eli Zaretskii <address@hidden> writes:
> And why was 99634.2.937 merged to the trunk, even though the log
> message clearly says it's a backport? If we avoid merging such
> backported revisions, will this problem go away?
A merge always includes all parent revisions. There is no way to "avoid
merging a backported revision".
Andreas.
--
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- Confusing "bzr log" as result of merges, Eli Zaretskii, 2011/05/21
- Re: Confusing "bzr log" as result of merges,
Andreas Schwab <=
- Re: Confusing "bzr log" as result of merges, Eli Zaretskii, 2011/05/21
- Re: Confusing "bzr log" as result of merges, Eli Zaretskii, 2011/05/21
- Re: Confusing "bzr log" as result of merges, Sven Joachim, 2011/05/21
- Re: Confusing "bzr log" as result of merges, Eli Zaretskii, 2011/05/21
- Re: Confusing "bzr log" as result of merges, Sven Joachim, 2011/05/21
- Re: Confusing "bzr log" as result of merges, Eli Zaretskii, 2011/05/21
- Re: Confusing "bzr log" as result of merges, Sven Joachim, 2011/05/21
- Re: Confusing "bzr log" as result of merges, Andreas Schwab, 2011/05/21
- Re: Confusing "bzr log" as result of merges, Eli Zaretskii, 2011/05/21
- Re: Confusing "bzr log" as result of merges, Andreas Schwab, 2011/05/21