Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tizen: Supported a custom gbs conf file #697

Merged
merged 1 commit into from
Jan 14, 2021
Merged

Conversation

leemgs
Copy link
Collaborator

@leemgs leemgs commented Jan 14, 2021

This commit is to support a custom gbs conf file.
If the ./packaging/.gbs.conf file exists, the gbs build uses this file.
If the ./packaging/.gbs.conf file does not exist, the gbs build uses
~/.gbs.conf file.

Signed-off-by: Geunsik Lim geunsik.lim@samsung.com


This commit is to support a custom gbs conf file.
If the ./packaging/.gbs.conf file exists, the gbs build uses this file.
If the ./packaging/.gbs.conf file does not exist, the gbs build uses
~/.gbs.conf file.

Signed-off-by: Geunsik Lim <geunsik.lim@samsung.com>
@taos-ci
Copy link
Collaborator

taos-ci commented Jan 14, 2021

📝 TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #697. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

Copy link
Collaborator

@taos-ci taos-ci left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nnstreamer, 💯 All CI checkers are successfully verified. Thanks.

@leemgs leemgs deleted the upstream-gbs-custom-conf branch January 28, 2021 02:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants