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
fsmonitor--daemon: on macOS support symlink #1406
Conversation
Resolves a problem where symbolic links were not showing up in diff when created or modified. kFSEventStreamEventFlagItemIsSymlink is also treated as a file update. This is because kFSEventStreamEventFlagItemIsFile is not included in FSEvents when creating or deleting symbolic links. For example: $ ln -snf t test fsevent: '/path/to/dir/test', flags=0x40100 ItemCreated|ItemIsSymlink| $ ln -snf ci test fsevent: '/path/to/dir/test', flags=0x40200 ItemIsSymlink|ItemRemoved| fsevent: '/path/to/dir/test', flags=0x40100 ItemCreated|ItemIsSymlink| Signed-off-by: srz_zumix <zumix.cpp@gmail.com>
Welcome to GitGitGadgetHi @srz-zumix, 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. You can CC potential reviewers by adding a footer to the PR description with the following syntax:
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, |
/allow |
User srz-zumix is now allowed to use GitGitGadget. |
/preview |
Preview email sent as pull.1406.git.1667884930833.gitgitgadget@gmail.com |
/submit |
Submitted as pull.1406.git.1667885119570.gitgitgadget@gmail.com To fetch this version into
To fetch this version to local tag
|
On the Git mailing list, Taylor Blau wrote (reply to this): On Tue, Nov 08, 2022 at 05:25:19AM +0000, srz_zumix via GitGitGadget wrote:
> From: srz_zumix <zumix.cpp@gmail.com>
>
> Resolves a problem where symbolic links were not showing up in diff when
> created or modified.
Looks reasonable to me. Adding Jeff Hostetler (cc'd) as a possible
reviewer.
Thanks,
Taylor |
User |
This branch is now known as |
This patch series was integrated into seen via git@1d9e34b. |
This patch series was integrated into seen via git@c573e9d. |
This patch series was integrated into seen via git@1cb305e. |
On the Git mailing list, Jeff Hostetler wrote (reply to this): On 11/8/22 4:35 PM, Taylor Blau wrote:
> On Tue, Nov 08, 2022 at 05:25:19AM +0000, srz_zumix via GitGitGadget wrote:
>> From: srz_zumix <zumix.cpp@gmail.com>
>>
>> Resolves a problem where symbolic links were not showing up in diff when
>> created or modified.
> > Looks reasonable to me. Adding Jeff Hostetler (cc'd) as a possible
> reviewer.
> > Thanks,
> Taylor
This looks good to me too. Thanks! |
User |
This patch series was integrated into seen via git@ca584d2. |
This patch series was integrated into seen via git@5ed52af. |
This patch series was integrated into seen via git@2194574. |
This patch series was integrated into seen via git@b561c80. |
This patch series was integrated into seen via git@7eaa009. |
This patch series was integrated into seen via git@3ddcd1e. |
This patch series was integrated into seen via git@9d2f4f3. |
This patch series was integrated into seen via git@de31768. |
This patch series was integrated into next via git@ad972b3. |
This patch series was integrated into seen via git@7a99b5a. |
This patch series was integrated into seen via git@a19c111. |
This patch series was integrated into seen via git@404ced6. |
There was a status update in the "Cooking" section about the branch Fix an issue where core.fsmonitor on macOS would not notice created or modified symbolic links. Will merge to 'master'. source: <pull.1406.git.1667885119570.gitgitgadget@gmail.com> |
This patch series was integrated into seen via git@8d7b35b. |
This patch series was integrated into master via git@8d7b35b. |
This patch series was integrated into next via git@8d7b35b. |
Closed via 8d7b35b. |
Resolves a problem where symbolic links were not showing up in diff when created or modified.
(on macOS with git config core.fsmonitor=true)
cc: Taylor Blau me@ttaylorr.com
cc: Jeff Hostetler git@jeffhostetler.com