Git FAQ - "How to handle changes that should not merge upward?"
| From: | Bishop Bettini | Date: | Fri, 17 May 2019 14:55:54 +0000 |
| Subject: | Git FAQ - "How to handle changes that should not merge upward?" | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-105733@lists.php.net to get a copy of this message | ||
Our Git FAQ[1] currently says (at the bottom):
> What about commits that should not be merged upwards (say, only for 5.3)?
Should you still merge them but make it so no changes actually take place?
Otherwise, it will the next person merging that will have to deal with the
conflict (or worse, the changes will be merged when they shouldn't have
been)
Please, could someone supply examples as to when this scenario occurs, and
how to handle it?
[1]: https://wiki.php.net/vcs/gitfaq