Avoid merge commits in gerrit/git -


here scenario.

  1. developer pushes commit c1 gerrit based on commit c
  2. developer b pushes commit c2 gerrit based on commit c
  3. reviewer merges commits c1 , c2 in gerrit.
  4. when reviewer pulls repo (using git pull --rebase), he/she sees 3 commits.

(last shown on top, shown in git log)

merge "log_message_of_commit_c2" master (this not have change id)

log_message_of_commit_c2

log_message_of_commit_c1

was merge commit created gerrit when c2 merged after c1? there way avoid this? (other developer b rebasing , resubmitting c2, involves synchronization between , b, not possible)

thanks, sameer

the merge-commit created gerrit.

you can avoid merge commits using cherry-pick strategy in gerrit. see: https://gerrit-review.googlesource.com/documentation/project-configuration.html#submit_type


Comments

Popular posts from this blog

jquery - How do you format the date used in the popover widget title of FullCalendar? -

asp.net mvc - SSO between MVCForum and Umbraco7 -

Python Tkinter keyboard using bind -