8000 Minor fixes based on comments in the thread. · ilustreous/matplotlib@4b7f4b8 · GitHub
[go: up one dir, main page]

Skip to content

Commit 4b7f4b8

Browse files
committed
Minor fixes based on comments in the thread.
1 parent 13419cc commit 4b7f4b8

File tree

1 file changed

+4
-15
lines changed

1 file changed

+4
-15
lines changed

doc/devel/gitwash/development_workflow.rst

Lines changed: 4 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -82,12 +82,12 @@ In more detail
8282
# (use "git add <file>..." to update what will be committed)
8383
# (use "git checkout -- <file>..." to discard changes in working directory)
8484
#
85-
# modified: README
85+
# modified: README
8686
#
8787
# Untracked files:
8888
# (use "git add <file>..." to include in what will be committed)
8989
#
90-
# INSTALL
90+
# INSTALL
9191
no changes added to commit (use "git add" and/or "git commit -a")
9292

9393
#. Check what the actual changes are with ``git diff`` (`git diff`_).
@@ -151,7 +151,8 @@ When you are ready to ask for the merge of your code:
151151

152152
#. If the branch is to be merged into a maintenance branch on the main
153153
repo, make sure the "base branch" indicates the maintenance branch
154-
and not master.
154+
and not master. Github can not automatically determine the branch
155+
to merge into.
155156

156157
Staying up to date with changes in the central repository
157158
=========================================================
@@ -197,24 +198,12 @@ If you were to merge ``upstream/master`` to your ``master``, you
197198
would start to diverge from the upstream. If this command fails, see
198199
the section on accidents_.
199200

200-
.. Doesn't one then need to push this up to the private repository? I
201-
.. have multiple machines I use for development, and I don't want to
202-
.. have to do this on all of them - MGD
203-
204-
.. Not really; does the paragraph below explain this enough? - JKS
205-
206201
The letters 'ff' in ``--ff-only`` mean 'fast forward', which is a
207202
special case of merge where git can simply update your branch to point
208203
to the other branch and not do any actual merging of files. For
209204
``master`` and other integration branches this is exactly what you
210205
want.
211206

212-
.. Does this need to be done for each maintenance branch as well?
213-
.. This doesn't seem to be sufficient to pull in changes on an
214-
.. upstream maintenance branch. - MGD
215-
216-
.. Does the section below answer this? - JKS
217-
218207
Other integration branches
219208
--------------------------
220209

0 commit comments

Comments
 (0)
0