# Nested grouping of commits?

**URL:** <https://discourse.pijul.org/t/nested-grouping-of-commits/279>\
**Category:** Question\
**Created:** [February 5, 2019, 6:41pm UTC](https://discourse.pijul.org/t/nested-grouping-of-commits/279 "2019-02-05T18:41:24Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![no\_identd](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.pijul.org/no_identd/32/126_2.png) [@no\_identd](https://discourse.pijul.org/u/no_identd)\
**Post date:** [July 22, 2020, 3:12pm UTC](https://discourse.pijul.org/t/nested-grouping-of-commits/279/5 "2020-07-22T15:12:26Z")

</div>

> [@Patching patches](https://discourse.pijul.org/t/patching-patches/212):
>
> Here is a feature that someone suggested to me today: patches that operate on other patches rather than on the direct text. One potential implementation (but I have other ideas as well) could be to represent some patches as plain text files, added to the repository as normal files (for example in a patches directory at the top level), and patchable themselves. When a patch is patched, a cascade of unrecords + application of the new version would follow (the cascade is needed because this would …

🤔

---

_[View the full topic](https://discourse.pijul.org/t/nested-grouping-of-commits/279)._