4 ms·

hg branch new-feature If you want it to branch from a different changeset than the one you're on, then: hg update deadbeef hg branch new-feature No flags

by tghw 17y ago

hg branch new-feature If you want it to branch from a different changeset than the one you're on, then: hg update deadbeef hg branch new-feature No flags, no orgin/newfeature (what does that even mean?), just the commands describing exactly what you're doing.

jshen 17y ago
# this creates the branch and switches to it (i.e. does a checkout) git checkout -b new-feature The only diff is -b, which is fine to me because it makes it clear that you are doing two things. You don't need the origin/newfeature stuff for the common case. I'm assuming this is what 'hg branch new-feature' is doing. How do you create a branch and not switch to it?
- tghw 17y ago
  > How do you create a branch and not switch to it? hg branch new-feature hg update default But why would you not want to switch to a branch you just created? Why create the branch if you're not going to work on it?
  - jshen 17y ago
    I don't presume to know what is necessary by everyone's situation. If the argument is that mercurial is better because you don't have to use -b, well that's weak sauce.
    - davidw 17y ago
      I actually use git, myself, but it's not just the -b; there's all kind of stuff like that in git's "user interface". It gets annoying at times.
      - davidw 17y ago
        Also, while it makes it 'a bit annoying' for people like me, I wonder if it will rule git out when it comes to Big Companies and people who are not so computer literate. The last time I looked at the git/windows thing, it was pretty ugly and not nearly as easy to use as turtlesvn.
        jshen 17y ago
        i'm at a big company that everyone has heard of, and we use git.
        davidw 17y ago
        Without more information, I can't really say if you're contradicting me thesis or not. I can easily imagine a small group of git users in any big company, but not so much a larger group that includes a lot of less technical users.
  - stevelosh 17y ago
    Actually that won't create a new branch. 'hg branch foo' just marks the working directory as branch foo. The 'hg update default' would then update back to the default branch and mark the working directory as being on 'default'. To really just create a new branch you do: 'hg branch foo; hg commit -m "Create a new branch."' Two steps, but like you said, it's probably not something you'd be doing very often anyway.

by tghw 17y ago

jshen 17y ago

# this creates the branch and switches to it (i.e. does a checkout) git checkout -b new-feature The only diff is -b, which is fine to me because it makes it clear that you are doing two things. You don't need the origin/newfeature stuff for the common case. I'm assuming this is what 'hg branch new-feature' is doing. How do you create a branch and not switch to it?

tghw 17y ago
> How do you create a branch and not switch to it? hg branch new-feature hg update default But why would you not want to switch to a branch you just created? Why create the branch if you're not going to work on it?
- jshen 17y ago
  I don't presume to know what is necessary by everyone's situation. If the argument is that mercurial is better because you don't have to use -b, well that's weak sauce.
  - davidw 17y ago
    I actually use git, myself, but it's not just the -b; there's all kind of stuff like that in git's "user interface". It gets annoying at times.
    - davidw 17y ago
      Also, while it makes it 'a bit annoying' for people like me, I wonder if it will rule git out when it comes to Big Companies and people who are not so computer literate. The last time I looked at the git/windows thing, it was pretty ugly and not nearly as easy to use as turtlesvn.
      - jshen 17y ago
        i'm at a big company that everyone has heard of, and we use git.
        davidw 17y ago
        Without more information, I can't really say if you're contradicting me thesis or not. I can easily imagine a small group of git users in any big company, but not so much a larger group that includes a lot of less technical users.
- stevelosh 17y ago
  Actually that won't create a new branch. 'hg branch foo' just marks the working directory as branch foo. The 'hg update default' would then update back to the default branch and mark the working directory as being on 'default'. To really just create a new branch you do: 'hg branch foo; hg commit -m "Create a new branch."' Two steps, but like you said, it's probably not something you'd be doing very often anyway.