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

When merging into master the release branch is always preferred, so let t #153

Closed
wants to merge 1 commit into from
Closed

Conversation

Bertg
Copy link

@Bertg Bertg commented Sep 16, 2011

When merging into master the release branch is always preferred, so let the merge know and prevent conflicts.
Using the recursive/theirs strategy the release is always preferred.

…et the merge know and prevent conflicts.

Using the recursive/theirs strategy the release is always preferred.
@gvangool
Copy link

Not necessarily, given following setup

    + B ---- C ---- D ---- E
   /   \     \
  /     \     +-- G ---+
 /       +-- F --+      \ 
/                 \      \
A ---------------+ H ---+ I

I should be able to contain fixes from H and G

@Bertg
Copy link
Author

Bertg commented Sep 16, 2011

I'm not to sure about that. If F and G same lines in same files (e.g.: version bump) it can cause a collision. That's what has happened to us.

It's also nice just to be on the safe side.

@Bertg Bertg closed this Oct 7, 2014
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

Successfully merging this pull request may close these issues.

None yet

2 participants