rhinooreo.blogg.se - Does git checkout readwrite

#Does git checkout readwrite how to
#Does git checkout readwrite code

Pushing to poky-contrib git push -u poky-contrib branch-name:remote-branch-name

When your changes are ready, you can push them: "michaelw/fixes-thing".Īdd changes to this branch ensuring commit messages follow the standard format defined below. The convention is that the branch name contains your name followed by a forward slash and then the topic of the branch e.g. Read-only: $ git clone git:///Ĭreate a branch, originating at the tip, that you will push: For any other repository at that is not Poky, you can just clone it either read-only or read-write as follows: The process is simple for contributions that are not based off of the Poky repository. Read-write: $ git remote add poky-contrib Clone a (non-Poky) Repository from Read-only: $ git remote add poky-contrib git:///poky-contrib Execute only one of the two following instructions: You have the option to add the poky-contrib remote as a read-only (perhaps for the case where you haven't sent the ssh access keys) or as read-write if you have cleared your write access as indicated in Poky_Contributions#Request_Access. $ git clone git:///poky Add poky-contrib as a Git Remote You can skip to the Clone a Repository from section if you are not working in the poky-contrib repository, not all the repositories require this double relationship for contributions.Ĭlone the main git tree (if you haven't already):

Publish your contributions to the poky-contrib repository.

#Does git checkout readwrite code

Base your code changes from the poky repository.

#Does git checkout readwrite how to

The first part of the git workflow explanation intends to let you know how to use these two repositories for: For contributions, there exists poky-contrib. Poky is a read-only repository that only the maintainers are able to write to. Where existing user branches can be seen. You might want to use git remote to pull from the master poky tree so that you pull in updates from there. Once you have access, you will be able to clone and push any of the other repositories at.

See to see which prefixes are already in use.

Include your preferred branch prefix for *-contrib repositories.

List the repositories you're planning to contribute to.

If you don't have one generate it by running ssh-keygen -t ed25519 -C Find you public key at ~/.ssh/id_ed25519.pub

Attach your ssh public key which usually named id_rsa.pub or id_ed25519.pub.

To write to a repo on, including poky-contrib, please send an email to the helpdesk and: Consider that poky-contrib is the most solicited repo so it is also the example that appears in the guide. If you need to contribute to any of these repos you can follow the instructions below. There are a number of git repositories at the Yocto Project git server.

Richard/Saul pulls target branch into Poky upstreamĪccess to Repositories.

Revise your branch based on comments and jump back to step 2 for another merge request.

If all patches in the branch are in good form, jump to step 7.

Quotes should be provided instead of simply providing comments. If there are some improvements or further discussion required, Richard/Saul will reply with explanation in mail.

Once seeing the merge mail, either Richard or Saul will check candidate patches in target poky-contrib branch.

Send the merge mail to the poky mailing list as possible, with notes:.

Compose a merge mail based on above body information, plus:.

When you're ready for submission, compose a merge message by running this script:.

Keep all of your own changes in the poky-contrib tree before requesting for acceptance.

4.3 Clone a (non-Poky) Repository from.