-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
(cherry picked from commit ce45d0e)
- Loading branch information
Showing
5 changed files
with
9 additions
and
9 deletions.
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
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
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
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
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
eea10a7
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.
Should this really be in 3.5?
With this I get a massive red blob for some repos (when submodule changes are tested on them), green looked better.
Following Git for functionality is one thing, colors and design is another...
eea10a7
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.
eea10a7
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 has not been more than a few days in master. I am tempted to request a revert in the default setup...
There is not much time for feedback for release candidates.
eea10a7
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.
@gerhardol Do you have the possibility to share a screenshot so that everyone could make its own point of view on the case you encounter?
eea10a7
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.
I can add local branches to every commit and flip back the colors, but that is for tonight
eea10a7
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.
eea10a7
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.
A "product" repo has certain configuration many submodules consisting of build system, applications and platform functionality.
In other SW, the submodules would basically be libraries. This is embedded SW though, so many changes will affect the configuration and code in the product repo. Some of these updates can take a long time, there are different strategies to prefill caches for these progression builds.
So basically every push to the submodules are testes on the product repo in progression builds, to give feedback to the submodule developers.
So there are a lot of branches in the product repos.
Branch names are generated, often total over 100 chars.
So with this you get a big red text in your face, the green was more welcoming.
eea10a7
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.
faked labels, it looks more intimating with different names
eea10a7
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.
😉
eea10a7
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.
When I see that, I think perhaps he wants the same kind of options that we have for repository path:
eea10a7
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.
But I want to see the remote branches...
Almost, but there is a tail I omitted "/on/master", "on/release/3.5" so it is not exactly the last part...
Limit to last 32 chars or so would be OK for me.
#8900 looks better though
eea10a7
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.