Skip to content
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.

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

FAQ item 2.25 is unclear #52907

Closed
exarkun mannequin opened this issue May 8, 2010 · 3 comments
Closed

FAQ item 2.25 is unclear #52907

exarkun mannequin opened this issue May 8, 2010 · 3 comments
Assignees

Comments

@exarkun
Copy link
Mannequin

exarkun mannequin commented May 8, 2010

BPO 8661
Nosy @brettcannon, @orsenthil

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = 'https://github.com/brettcannon'
closed_at = <Date 2011-06-27.00:35:09.395>
created_at = <Date 2010-05-08.15:33:40.626>
labels = []
title = 'FAQ item 2.25 is unclear'
updated_at = <Date 2011-06-27.00:35:09.393>
user = 'https://bugs.python.org/exarkun'

bugs.python.org fields:

activity = <Date 2011-06-27.00:35:09.393>
actor = 'brett.cannon'
assignee = 'brett.cannon'
closed = True
closed_date = <Date 2011-06-27.00:35:09.395>
closer = 'brett.cannon'
components = []
creation = <Date 2010-05-08.15:33:40.626>
creator = 'exarkun'
dependencies = []
files = []
hgrepos = []
issue_num = 8661
keywords = []
message_count = 3.0
messages = ['105300', '105306', '139232']
nosy_count = 3.0
nosy_names = ['brett.cannon', 'exarkun', 'orsenthil']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = None
status = 'closed'
superseder = None
type = None
url = 'https://bugs.python.org/issue8661'
versions = []

@exarkun
Copy link
Mannequin Author

exarkun mannequin commented May 8, 2010

The item "How do I prepare a new branch for merging?" is unclear about which branch needs to be prepared. It could be the source branch or the destination branch. In #python-dev, I learned that it's probably the destination branch being discussed here. This should be clarified (and it could also be pointed out that it is almost always the case that this step has been done by someone else already).

@orsenthil
Copy link
Member

I would also suggest a re-ordering of FAQ entries in this manner:

1st What tools do I need to merge between branches?
2nd How do I merge between branches?

And then,

How do I prepare a new branch for merging?

With the explanation/clarification.

@brettcannon
Copy link
Member

This is out of date thanks to the rewrite of the FAQ for Mercurial.

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants