Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
N notebook
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mark Stevens
  • notebook
  • Wiki
  • the problem with updating sources

Last edited by Mark Stevens Nov 28, 2016
Page history

the problem with updating sources

updating sources from remote trees

Sources from remote trees creates a problem because some sources use repo/git to separate out projects into individual repos and then they are combined into a single large project using Repo (python wrapper around git to manage multiple repositories much more cleanly than git subtrees)

Other sources (mainly from china) dispense with the complications of managing multiple repos and simply create a single repo with all the source as one project. This is easier for them to maintain, but it creates a level of distance from the original source and it's updates. This allows the maintainers to make changes throughout the code base while protecting them from the complexities of merging updates.

We are caught in the middle. Our devices would be more easily managed if projects could be shared among multiple devices from different manufacturers, but any updates we make in the core source can't easily be managed in this fashion. In order to pull updates from the source, our project tree must include the source as it exists in the remote repo (by device mfr). If we use repo, then the changed source must be merged from the monolithic project to the disparate projects, preferrably with the commit history intact.

Clone repository
  • branch code plan
  • build and test configuration
  • build artifact versioning
  • build server instrumented testing
  • build server move
  • bzt16wifi02 releases
  • bzt18uxa02 releases
  • configuration settings and permissions
  • create a repo from cli in gitlab
  • engineering status
  • feature deployment
  • gitlab installation instructions
  • Home
  • ota update and deployment
  • qbert implementation
View All Pages