Start using new git-extra prefix (follow-up) #460
Conversation
dennisameling
force-pushed
the
git-extra-new-prefix
branch
from
af1fdc6 to
c0e0a7a
Compare
dennisameling
changed the title
|
UPDATE Jan 22nd 2023: the error below no longer applies. Ha, interesting. CI is failing with the following error: That's because the changes we need to install So we could e.g. take the first three commits, c0e0a7a, 26350da and d98adb1, and open a separate PR for those, merge it, let the UPDATE: I'm optimistic that'll work. For example, |
dennisameling
changed the title
In a recent commit, we started publishing the mingw-w64-git-extra package in addition to git-extra. We intend to completely remove the old git-extra package over time, but let's start using the new mingw-w64-git-extra prefix now. More background on this change can be found in the attached commit. Ref: git-for-windows@3f26b1b Signed-off-by: Dennis Ameling <[email protected]>
In a recent commit, we started publishing the mingw-w64-git-extra package in addition to git-extra. We intend to completely remove the old git-extra package over time, but let's start using the new mingw-w64-git-extra prefix now. More background on this change can be found in the attached commit. Ref: git-for-windows@3f26b1b Signed-off-by: Dennis Ameling <[email protected]>
dennisameling
force-pushed
the
git-extra-new-prefix
branch
from
7f17faf to
e9766d2
Compare
2 participants
⚠️ This needs #457 to be merged first⚠️ This needs #461 to be merged firstI used the list of files that need updating from this comment (thanks @dscho!)
Let's leave the rename of the
git-extrafolder tomingw-w64-git-extrafor a follow-up PR.Important note regarding Wiki updates: the updates to the wiki currently live on a branch that are not accessible through GitHub's UI. To see them, do the following:
As we can't create a PR for the changes from that branch, we'll have to commit straight to the
mainbranch if all looks good. CC @dscho