[PATCH 4/4] Add a ./bootstrap script to automate bundling and generating files

[Joseph Myers]

On Fri, 7 Jun 2024, Luke T. Shumaker wrote:

> Even after the two are in better sync, I think that having 'patches/'
> as a live a record of "changes that still need to be copied over" is
> probably a pretty good workflow; in many cases they can even be
> applied with `git am` and sent with `git send-email`.  So, for
> example: whatever.patch is approved to binutils; and is commited to
> binutils.git/libiberty/patches/whatever.patch.  That patch is then
> applied to GCC.  The next time someone bumps the commit hash in
> binutils.git/bootstrap.d/bundle-gcc.mk ty sync with GCC, `patch` will
> complain that the patch has already been applied, and then the person
> can delete the patch file.

That process still seems excessively complicated.

Preferred process:

* Precondition: the shared files and directories are in sync.  (Files such 
as Makefile.def are definitely included in this, not just shared 
subdirectories.)

1. A patch is committed to both places.

* Postcondition: the shared files and directories are still in sync.

You seem to be suggesting a more complicated process involving committing 
to one place, also committing a .patch file there, committing to the other 
place, then doing a second commit to the first place to remove the .patch 
file and update a commit hash.

-- 
Joseph S. Myers
josmyers@redhat.com