Le 29/10/2026 à 23:17, Jason Lingohr a écrit :
On 30/10/26 01:44, Eric Covener wrote:
This sentence seems wrong:
The developers continue to seek to maintain module compatibility between 2.4.1
and future 2.4 releases for administrators and end users.
Zap entirely?
As with Lucien’s comment, I’m not sure exactly how I’d apply the same patch to
2.4 and Trunk in the actual Git-native way. I’m sure I’ll figure out
workarounds, but it would be nice to know the actual “correct” way to do it.
A simple option is to clone it twice in sibling directories and treat
it like your SVN checkouts.
Heya, I've done some tweaks that hopefully addresses the latest stuff
mentioned here.
https://httpd-devnotes-feedback.staged.apache.org/dev/devnotes.html
Thanks Jason, great job ; things are much clearer yet !
I’ll try this procedure, and come back here.
--- One suggestion : if more than one file is modified, instead of
committing each file one by one, what about using the -a option :
instead of :
|% git add docs/manual/bind.xml.fr|
|% git commit -m "Update French translation of bind.xml"
|
|use :|
|% git commit -a -m "Update French translation of bind.xml"|
||
which commits all files that have been modified.
--- One question : what is the purpose of creating a new branch ? (
|% git switch -c bind-fr-update|
||
||
Why not directly committing the changes with "git push" ?
