Drop all hg-related questions from the FAQ. #71
Merged
Conversation
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
Questions already moved were left. Otherwise Git is covered well enough online that we should avoid duplicating documenting anything that isn't specific to our suggested workflow.
Mariatta
reviewed
Oct 28, 2016
| @@ -181,8 +183,8 @@ best to run a ``make distclean`` to ensure that all previously built files | |||
| are removed. | |||
|
|
|||
|
|
|||
| I want to keep a separate working copy per development branch, is it possible? | |||
| '''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''' | |||
| I want to keep a separate working copy per development branch, is it's possible? | |||
There was a problem hiding this comment.
is it possible?
instead of is it's possible
There was a problem hiding this comment.
Heh, my brain read it as "if its possible", hence the word change.
There was a problem hiding this comment.
We might also suggest git worktree here, I've used it some and it works pretty well. Equivalent to hg share.
(This comment not especially relevant to this PR, just getting it out there before I forget about it.)
There was a problem hiding this comment.
Personally I'd prefer a more explicit form of question:
Can I keep a separate working copy per development branch?
How do I keep a separate working copy per development branch?
AA-Turner
pushed a commit
to AA-Turner/devguide
that referenced
this pull request
Jun 17, 2022
Questions already moved were left. Otherwise Git is covered well enough online that we should avoid duplicating documenting anything that isn't specific to our suggested workflow.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Questions already moved were left. Otherwise Git is covered well enough online
that we should avoid duplicating documenting anything that isn't specific to
our suggested workflow.
Closes #48