geda:scm
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
geda:scm [2015/10/27 19:12] kaimartin moved "format a patch" more to the top as it affects users with read access |
geda:scm [2016/08/04 12:35] (current) kaimartin [Track a feature branch] removed spurious brackets |
||
|---|---|---|---|
| Line 9: | Line 9: | ||
| * [[https://www.atlassian.com/git/tutorials/|comprehensive set of tutorials]] at atlassian.com | * [[https://www.atlassian.com/git/tutorials/|comprehensive set of tutorials]] at atlassian.com | ||
| * [[https://git.wiki.kernel.org/index.php/GitSvnCrashCourse|GitSvnCrashCourse]] -- git courses for SVN users | * [[https://git.wiki.kernel.org/index.php/GitSvnCrashCourse|GitSvnCrashCourse]] -- git courses for SVN users | ||
| - | * [[http://git.huit.harvard.edu/guide/ Git, the simple guide]] -- very concise and condensed cheat sheet style tutorial | + | * [[http://git.huit.harvard.edu/guide/| Git - The Simple Guide]] -- very concise and condensed cheat sheet style tutorial |
| ===== Read-only access the geda repositories ===== | ===== Read-only access the geda repositories ===== | ||
| Line 28: | Line 28: | ||
| ==== List all branches of a project ==== | ==== List all branches of a project ==== | ||
| - | To list all branches of a project available on the geda-project server emit this command: | + | To list all branches of a project available on the geda-project server cd to your local copy of the project and emit this git command: |
| - | <code>$ git ls-remote git://git.geda-project.org/geda-gaf.git</code> | + | <code>$ git branch -r</code> |
| ==== Track a feature branch ==== | ==== Track a feature branch ==== | ||
| This will create a branch with the name ''<local name>'' in your local repository, which tracks the ''<remote name>'''d branch. | This will create a branch with the name ''<local name>'' in your local repository, which tracks the ''<remote name>'''d branch. | ||
| <code>$ git checkout --track -b <local name> origin/<remote name></code> | <code>$ git checkout --track -b <local name> origin/<remote name></code> | ||
| - | Go ahead and build the application]] from the branch as described by the [[geda:gaf_building_git_version|build instructions]]. By default the command ''make install'' will copy the binaries to ''/usr/local/*''. That way, it will not interfere with an install done by your linux distribution. You may use full paths, symbolic links or aliases to pick which version to use. | + | Go ahead and build the application from the branch as described by the [[geda:gaf_building_git_version|build instructions]]. By default the command ''make install'' will copy the binaries to ''/usr/local/*''. That way, it will not interfere with an install done by your linux distribution. You may use full paths, symbolic links or aliases to pick which version to use. |
| + | |||
| + | ==== Communicate your experience ==== | ||
| + | Generally, there will be a launchpad bug associated with the feature of the branch. Please report your experience with the branch there. Your input will influence whether or not the feature will make into mainstream. There is a group of users and developers who keep an eye on changes to bug reports. They will get noticed by email. | ||
| + | |||
| + | For additional visibility you may report your experience on the mailing list [[geda:mailinglists|geda-user]]. It may even spark a discussion. As with all forms of general online discussion, the note may get archived and gradually be forgotten without any action taken. | ||
| ===== Format a patch to send to the developers ===== | ===== Format a patch to send to the developers ===== | ||
| Line 46: | Line 50: | ||
| $ git format-patch -1 # create a patch file based on that commit | $ git format-patch -1 # create a patch file based on that commit | ||
| This will output a filename which contains the patch. Be sure to look at the documentation for format-patch for more information. This file can be e-mailed to developers who have write access and can be applied using git apply. | This will output a filename which contains the patch. Be sure to look at the documentation for format-patch for more information. This file can be e-mailed to developers who have write access and can be applied using git apply. | ||
| - | |||
| - | ==== Communicate your experience ==== | ||
| - | Generally, there will be a launchpad bug associated with the feature of the branch. Please report your experience with the branch there. Your input will influence whether or not the feature will make into mainstream. There is a group of users and developers who keep an eye on changes to bug reports. They will get noticed by email. | ||
| - | |||
| - | For additional visibility you may report your experience on the mailing list [[geda:mailinglists|geda-user]]. It may even spark a discussion. As with all forms of general online discussion, the note may get archived and gradually be forgotten without any action taken. | ||
| ===== Access the repository with write permission ===== | ===== Access the repository with write permission ===== | ||
geda/scm.1445987537.txt.gz · Last modified: 2015/10/27 19:12 by kaimartin
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
