[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Confusing "bzr log" as result of merges
From: |
Óscar Fuentes |
Subject: |
Re: Confusing "bzr log" as result of merges |
Date: |
Sat, 21 May 2011 19:00:36 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
Andreas Schwab <address@hidden> writes:
> Óscar Fuentes <address@hidden> writes:
>
>> Avoid cherry-picking. Always do merges.
>
> Cherry-picks are a fact of life. You cannot avoid them completely.
Never cherry-pick from emacs-common. Why would you cherry pick from
emacs-common into emacs-23 or trunk, instead of just merging?
>> Create a branch emacs-common and commit there all the changes
>> intended for emacs-23 and trunk.
>
> And how do you know with 100% reliability?
You don't know with 100% reliability. If a change committed into
emacs-common does not belong there, do the same you do with the rest of
wrong commits: revert it.
I'm not saying that the proposed schema is perfect, it simply is better
than what we do now.
- Re: Confusing "bzr log" as result of merges, (continued)
- 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, 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
- 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
Re: Confusing "bzr log" as result of merges, Óscar Fuentes, 2011/05/21
Re: Confusing "bzr log" as result of merges, Eli Zaretskii, 2011/05/21
Re: Confusing "bzr log" as result of merges, Glenn Morris, 2011/05/21