FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Gitwash clarifications by mdboom · Pull Request #24 · matplotlib/matplotlib · GitHub

  1. matplotlib
  2. matplotlib

Repository navigation

Gitwash clarifications #24

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.

Sign up for GitHub

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

Merged
mdboom merged 4 commits into from
Apr 4, 2011
Conversation 33 Commits 4 Checks 0 Files changed
Merged

Gitwash clarifications #24

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
586baec
Add some clarifications and comments to the gitwash instructions base…
astropy-buildbot Feb 26, 2011
649fcdd
Further gitwash clarifications
jkseppan Mar 11, 2011
13419cc
Fix minor typo
mdboom Apr 4, 2011
4b7f4b8
Minor fixes based on comments in the thread.
mdboom Apr 4, 2011
File filter

Filter by extension

Filter by extension .rst  (1) All 1 file type selected
Viewed files
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Unified
Split
Hide whitespace
Diff view
Unified
Split
Hide whitespace
Prev Previous commit
Next Next commit
Fix minor typo
  • Loading branch information
mdboom committed Apr 4, 2011
commit 13419cc66a443c83341f2da76793de58ebdb89bd
2 changes: 1 addition & 1 deletion doc/devel/gitwash/development_workflow.rst
Show comments
View file
Open in desktop
This file contains hidden or 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
Show hidden characters
Original file line number Diff line number Diff line change
Expand Up @@ -230,7 +230,7 @@ new branches off of it, update it from upstream::

But you don't necessarily have to have such a branch. Instead, if you
are preparing a bugfix that applies to the maintenance branch, fetch
from upstream and base your bugfix on the remote branch;:
from upstream and base your bugfix on the remote branch::

git fetch upstream
git checkout -b my-bug-fix upstream/v1.0.x
Expand Down
Back | FazBrowse Home | New Git URL