[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Release branch plans
From: |
Andreas Schwab |
Subject: |
Re: Release branch plans |
Date: |
Mon, 02 Apr 2012 19:21:55 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.94 (gnu/linux) |
Eli Zaretskii <address@hidden> writes:
> Could we _please_ do it the other way around this time? That is,
> commit to the trunk and merge to the branch?
How can that be correct? Most of the trunk commits are not supposed to
occur on the release branch.
> Merging from the branch makes it hard to find out where some changes
> came from and why, because history metadata says some revisions were
> merged, but their code was not really brought to the target branch.
Merges are supposed to merge everything.
Andreas.
--
Andreas Schwab, address@hidden
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
- Re: auth.texi (was: Release branch plans), (continued)
Re: Release branch plans, Andreas Schwab, 2012/04/02
Re: Release branch plans, Stefan Monnier, 2012/04/02
Re: Release branch plans, Eli Zaretskii, 2012/04/02
- Re: Release branch plans,
Andreas Schwab <=
- Re: Release branch plans, Eli Zaretskii, 2012/04/02
- Re: Release branch plans, Andreas Schwab, 2012/04/02
- Re: Release branch plans, Eli Zaretskii, 2012/04/02
- Re: Release branch plans, Glenn Morris, 2012/04/02
- Re: Release branch plans, Andreas Schwab, 2012/04/02
- Re: Release branch plans, Glenn Morris, 2012/04/02
- Re: Release branch plans, Glenn Morris, 2012/04/02
- Re: Release branch plans, Andreas Schwab, 2012/04/03
- Re: Release branch plans, Eli Zaretskii, 2012/04/03
- Re: Release branch plans, Stefan Monnier, 2012/04/03