-
Notifications
You must be signed in to change notification settings - Fork 47
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
1 addition
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
226a85d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This only works on the very new versions of git. Debian's git don't work.
226a85d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@korli If we're going to do this, we need to check git versions as part of it.
a) find the git version in haikuporter, and track what version of git we're using. Then check it before init.
b) revert until newer versions of git are more widely used.
226a85d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO we should just revert this commit for now, then.
226a85d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can retry without -b in case of failure.
226a85d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The branch rename command
git branch -M
should be available in older versions, which can be used instead.226a85d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The problem then is a git version upgrade of the machine could result in two different branch names.
226a85d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is it a problem?
226a85d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we really need to change the default branch name here? I think
master
means "master copy", I do not think it needs to be changed. If Git changes the default branch name in a future release, then that's fine, but I'm not sure we need to care about this so much, especially when nobody will even see the default branch name of these repos for the most part.226a85d
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Git 2.30 writes 10 lines of hints when we don't name the default branch explicitly (we don't care the branch name).