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
Enable auto-merge for meld to follow the vimdiff beharior #781
Conversation
Welcome to GitGitGadgetHi @sunlin7, and welcome to GitGitGadget, the GitHub App to send patch series to the Git mailing list from GitHub Pull Requests. Please make sure that your Pull Request has a good description, as it will be used as cover letter. Also, it is a good idea to review the commit messages one last time, as the Git project expects them in a quite specific form:
It is in general a good idea to await the automated test ("Checks") in this Pull Request before contributing the patches, e.g. to avoid trivial issues such as unportable code. Contributing the patchesBefore you can contribute the patches, your GitHub username needs to be added to the list of permitted users. Any already-permitted user can do that, by adding a comment to your PR of the form Both the person who commented An alternative is the channel
Once on the list of permitted usernames, you can contribute the patches to the Git mailing list by adding a PR comment If you want to see what email(s) would be sent for a After you submit, GitGitGadget will respond with another comment that contains the link to the cover letter mail in the Git mailing list archive. Please make sure to monitor the discussion in that thread and to address comments and suggestions (while the comments and suggestions will be mirrored into the PR by GitGitGadget, you will still want to reply via mail). If you do not want to subscribe to the Git mailing list just to be able to respond to a mail, you can download the mbox from the Git mailing list archive (click the curl -g --user "<EMailAddress>:<Password>" \
--url "imaps://imap.gmail.com/INBOX" -T /path/to/raw.txt To iterate on your change, i.e. send a revised patch or patch series, you will first want to (force-)push to the same branch. You probably also want to modify your Pull Request description (or title). It is a good idea to summarize the revision by adding something like this to the cover letter (read: by editing the first comment on the PR, i.e. the PR description):
To send a new iteration, just add another PR comment with the contents: Need help?New contributors who want advice are encouraged to join git-mentoring@googlegroups.com, where volunteers who regularly contribute to Git are willing to answer newbie questions, give advice, or otherwise provide mentoring to interested contributors. You must join in order to post or view messages, but anyone can join. You may also be able to find help in real time in the developer IRC channel, |
There is an issue in commit 5f873da042c7b8b610611af01edfa95f7e181c95: |
There is an issue in commit d38e8f93d8383b6c7ccf37edc8c1389fe1c0bb0c: |
/allow |
User sunlin7 is now allowed to use GitGitGadget. |
/submit |
merged, thanks all of you. |
I don't see this merged... |
awkward... I'll wait for the merge finished, then close this ticket. Thank you @dscho. |
Hi @dscho, it seems no event happened for this PR since May 7. |
If I were you, I would reply on the mailing list with a gentle ping. |
The mailing list is updated, look forward for merging. |
On the Git mailing list, Pratyush Yadav wrote (reply to this):
|
/submit |
/submit |
Error: 3b70fd0 was already submitted |
On the Git mailing list, Git Gadget wrote (reply to this):
|
On the Git mailing list, Junio C Hamano wrote (reply to this):
|
On the Git mailing list, David Aguilar wrote (reply to this):
|
/submit |
On the Git mailing list, wrote (reply to this):
|
@dscho it's my failed that I open two pages and I try submit on both pages. |
On the Git mailing list, wrote (reply to this):
|
This patch series was integrated into seen via f152f19. |
This patch series was integrated into seen via 30b6e6d. |
Make the mergetool used with "meld" backend behave similarly to "vimdiff" by telling it to auto-merge non-conflicting parts and highlight the conflicting parts when `mergetool.meld.useAutoMerge` is configured with `true`, or `auto` for detecting the `--auto-merge` option automatically. Helped-by: Đoàn Trần Công Danh <congdanhqx@gmail.com> Helped-by: David Aguilar <davvid@gmail.com> Signed-off-by: Lin Sun <lin.sun@zoom.us> Signed-off-by: Junio C Hamano <gitster@pobox.com>
This patch series was integrated into seen via 468db80. |
On the Git mailing list, Lin Sun wrote (reply to this):
|
User |
@sunlin7 how about force-pushing the update, and then |
On the Git mailing list, Junio C Hamano wrote (reply to this):
|
This patch series was integrated into seen via a98dad7. |
This patch series was integrated into seen via ca35cc9. |
This patch series was integrated into seen via afa52bd. |
Yes, the new iteration was picked up, but the downside of not using GitGitGadget is that there is no tagged version of v2, nor a range-diff, i.e. it makes it harder than necessary for people who want to follow this patch's evolution. OTOH a But then, should yet another iteration be necessary, using GitGitGadget would really confuse people, as that would be sent as "another" second iteration. I guess that |
@dscho thank you for comment, I'll submit for complete GitGitGadget flow. |
/submit |
Submitted as pull.781.v18.git.git.1599895268433.gitgitgadget@gmail.com To fetch this version into
To fetch this version to local tag
|
On the Git mailing list, Junio C Hamano wrote (reply to this):
|
On the Git mailing list, Lin Sun wrote (reply to this):
|
This patch series was integrated into seen via 65ffb34. |
This patch series was integrated into next via 01985a6. |
This patch series was integrated into seen via a3728d7. |
This patch series was integrated into seen via 0e16dc0. |
This patch series was integrated into seen via 1a4e36a. |
This patch series was integrated into seen via 4aff18a. |
This patch series was integrated into next via 4aff18a. |
This patch series was integrated into master via 4aff18a. |
Closed via 4aff18a. |
Hi, the mergetool "meld" does NOT merge the no-conflict changes, while
the mergetool "vimdiff" will merge the no-conflict changes and highlight
the conflict parts. This patch will make the mergetool "meld" similar
to "vimdiff", auto-merge the no-conflict changes, highlight conflict
parts.
cc: Lin Sun lin.sun@zoom.us