# Resyncing latest Sage 9 changes into a customised theme, within a Bedrock deploy

**URL:** https://discourse.roots.io/t/resyncing-latest-sage-9-changes-into-a-customised-theme-within-a-bedrock-deploy/12057
**Category:** sage
**Created:** 2018-03-28T16:24:37Z
**Posts:** 6
**Showing post:** 2 of 6

## Post 2 by @mmirus — 2018-03-28T17:22:01Z

Hey @mikesource - your current approach is probably as good as any. I suspect that most people don’t generally update their Sage themes from upstream unless there’s a specific change or fix they need to incorporate. Sage isn’t really designed that way (see [Keeping Sage Updated](https://discourse.roots.io/t/keeping-sage-updated/10587/2)). Doing a merge, manually copying changes, or [cherry picking commits](https://discourse.roots.io/t/sage-9-parent-child-theme/8696/2) are likely the best options.

---

_[View the full topic](https://discourse.roots.io/t/resyncing-latest-sage-9-changes-into-a-customised-theme-within-a-bedrock-deploy/12057)._