Sorry for the confusion. Let me rephrase. It would be easier for me to help you review and update this patch if we use patch files instead of raw diffs. The main reason is that a patch can represent a complete commit, whereas a diff cannot. It also complicates things that you're not attaching the diff as a file, so I have to manually copy and paste things, but that's relatively minor. As an example, with your patch for ORG-NEWS, the diff doesn't tell me how you want the commit message updated. I guess I'm also trying to reconcile your statements of "I am using git" with "I don't know how to do...a commit message". Do you mean you're not sure of the format? I'll get the diff you sent applied but please let me know what wording you want for the ORG-NEWS change.
Cheers, Derek On Wed, Jul 29, 2026 at 4:30 AM Perry Smith <[email protected]> wrote: > > > On Jul 28, 2026, at 20:45, Derek Chen-Becker <[email protected]> > wrote: > > If you're using git, the simplest way for this would be to apply my patch > against main using "git am <my patch file>" and then you can amend the > commit with the ORG-NEWS change. Then to create the patch you do "git > format-patch <hash or range>". If you're not familiar with git or don't > have it readily available I can apply your patch on my side. > > > I don’t really understand this message. The diff (previous email) > included all of the changes for this. The only thing it didn’t include was > the change to the commit. > > I am using git (which you can tell by examining the diff). > > I’m not clear how to proceed. > > Perry > > -- +---------------------------------------------------------------+ | Derek Chen-Becker | | GPG Key available at https://keybase.io/dchenbecker and | | https://pgp.mit.edu/pks/lookup?search=derek%40chen-becker.org | | Fngrprnt: EB8A 6480 F0A3 C8EB C1E7 7F42 AFC5 AFEE 96E4 6ACC | +---------------------------------------------------------------+
