Chris Apple 5a117b63cd Ensure that grc and gcp always have the correct ordering, regardless of how they were input (#261) (#253) ... Closes #253. Essentially the idea is this: When cherry picking a group of commits, most of the time you want to cherry pick oldest to newest. This means you have the lowest chance of having a conflict or error when reverting a commit. You most often want to revert from newest to oldest. Similarly prevents errors This commit does that, based on the wonderful suggestion on how to do that from @carlfriedrich in the linked ticket (#253).		2022-12-16 06:50:28 -08:00
..
git-forgit	Ensure that grc and gcp always have the correct ordering, regardless of how they were input (#261) (#253)	2022-12-16 06:50:28 -08:00