[Feature Request] Standardized AdobeRGB TIFF Metadata Formatting to Enable Windows Explorer Thumbnails

[aviduser1]

First of all, NegPy is an incredible tool for negative conversions. I am loving it! However, may I request a small quality-of-life feature regarding the way NegPy embeds the AdobeRGB color profile metadata when exporting TIFF files.

Currently, when exporting a 16-bit TIFF image using the AdobeRGB color profile, NegPy writes the raw cryptographic ICC signature tag into the file header. While this is technically correct according to ICC standards, Windows Explorer’s native thumbnail generator fails to parse it natively, causing exported images to drop back to generic system or blank icons. I would love to be able to see the actual image as a thumbnail in my folders before importing it into Photoshop for final editing.

Would it be possible to adjust the export or metadata-writing engine (via the underlying Python imaging or ICC profile library) so that it embeds the standard, consumer-friendly "Adobe RGB (1998)" text string descriptor alongside the raw signature tag?

What are your thoughts on a solution for this behavior, and is this something that could potentially be implemented in an upcoming update?

Thank you for considering this improvement to the software! Also, I tried saving as PNG as a workaround thinking it would save uncompressed 16 bit files, but they were 8 bit. Perhaps an option to choose would be great!

PS: If anyone in the community has a working workaround for this specific NegPy TIFF metadata behavior on Windows, I would love to know as well.

[radioproektor]

It also would be very useful to have an uncompressed TIFF option. With fast SSDs uncompressed TIFF just saves a lot of time during batch processing. Currently in NegPy only TIFF Deflate (ZIP) compression available.

[aviduser1]

I agree. All three options of TIFF saving should be left to the user. Uncompressed, ZIP and LZW.

Same for PNG, 16 bit and 8 bit, in case someone opts for that.

[thetalkingdrum]

@aviduser1 Hey, I tried but could not reproduce the Adobe RGB no thumbnail bug. Exported some scanner files to TIFF with Adobe RGB as the color space, and Windows 10 Explorer had no problems making thumbnails of my files. You might be running into something else. Also, the reason the files show up as A98C is that they are an open-source implementation: https://github.com/saucecontrol/Compact-ICC-Profiles, not because they use some special signature. It should be possible to have them display Adobe RGB (1998) as well, though.

Maybe you could share one of problem exports and the source file? Include export settings like linear, flat, print. It could be some other metadata Explorer is choking on. I recently had to make a PR to make JXL exports work in Adobe Bridge and Finder, as they carried over some camera metadata that broke the viewers. (#960).

[aviduser1]

Hi Marcin Thanks for looking into this strange issue I was having. This happened with both the PRINT and FLAT method of saving. These negatives were photographed with a Sony α7RII camera + VALOI Easy25 V2 scanning system. The Sony is configured to save RAW images with AdobeRGB profile. However, when working on a new roll of scans early this morning, I saw there was an update to version 0.55.0 available and after updating the problem ceased to exist. Since you wanted to inspect the issue yourself, I have attached a problem file here with the thumbnail issue (in red below), so you are aware and can file it away as a resolved issue. Also attached is the RAW scan from the Sony camera. Witness files are: NikonFE_RA_Rhyolite_NegPyFLAT19.tiff <---- *Is the file with the issue converted with the previous version of NegPy. Saved as FLAT. * The attached files are as-is from NegPy and Sony. _DSC7490.ARW <------- Original scan from VALOI system I have attached a couple of screenshots to show how the thumbnails looked in the Explorer window. All in all, it's working fine now, and a great pleasure to work with! Many thanks Avi NikonFE_RA_Rhyolite_NegPyFLAT19.tiff <https://drive.google.com/file/d/1aDfgbR32XCrbIT-gscunD7kGalp1ilgk/view?usp=drive_web> _DSC7490.ARW <https://drive.google.com/file/d/1ihIhC9lDJL2DzFH-VzbTLTFF9yTccLkN/view?usp=drive_web>

…

On Sat, Aug 29, 2026 at 2:28 AM thetalkingdrum ***@***.***> wrote: @aviduser1 <https://github.com/aviduser1> Hey, I tried but could not reproduce the Adobe RGB no thumbnail bug. Exported some scanner files to TIFF with Adobe RGB as the color space, and Windows 10 Explorer had no problems making thumbnails of my files. You might be running into something else. Also, the reason the files show up as A98C is that they an open-source implementation: https://github.com/saucecontrol/Compact-ICC-Profiles, not because they use some special signature. It should be possible to have them display Adobe RGB (1998) as well, though. Maybe you could share one of problem exports and the source file? Include the source (what camera/scanner) and export settings like linear, flat, print. It could be some other metadata your Explorer is choking on. I recently had to make a PR to make TIFF exports work in Adobe Bridge and Finder, as they carried over some camera metadata that broke the viewers. ( #960 <#960>). — Reply to this email directly, view it on GitHub <#990?email_source=notifications&email_token=B2ZMGVDWXAJTZRDQZWOMKXL5MKO47A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRHE3TEMRZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18197229>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B2ZMGVHROOOGFHGWEWKHXWT5MKO47AVCNFSNUABJKJSXA33TNF2G64TZHMYTCMRTG43DMNRQHE5UI2LTMN2XG43JN5XDWMJQG4YDGOBZHGQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/B2ZMGVCY4H2ASXTIRTDDITD5MKO47A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRHE3TEMRZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/B2ZMGVAJZAT5HDZQ43WBA735MKO47A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBRHE3TEMRZUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

-- -------------------------------------------------------------- PRIVILEGED AND CONFIDENTIAL COMMUNICATION This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

[thetalkingdrum]

Hi, great that it’s working now! The files don’t have the right permissions to be downloaded. I’m not Marcin, btw :)

[aviduser1]

My apologies, I didn't know your name and assumed it was Marcin. I am glad as well that the thumbnails are working after the update this morning. I gave the permissions you requested for the files, could you download them?

…

On Sun, Aug 30, 2026 at 1:18 AM thetalkingdrum ***@***.***> wrote: Hi, great that it’s working now! The files don’t have the right permissions to be downloaded. I’m not Marcin, btw :) — Reply to this email directly, view it on GitHub <#990?email_source=notifications&email_token=B2ZMGVEVFV5O7YPKSF5OC6T5MPPO5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGA2TAMBQUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18205000>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B2ZMGVBMY2ONPOX7G5OCVTT5MPPO5AVCNFSNUABJKJSXA33TNF2G64TZHMYTCMRTG43DMNRQHE5UI2LTMN2XG43JN5XDWMJQG4YDGOBZHGQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/B2ZMGVEXAKLPGSNG27FCJR35MPPO5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGA2TAMBQUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/B2ZMGVAMRQ5TI23QU5PXAZD5MPPO5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGA2TAMBQUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

-- -------------------------------------------------------------- PRIVILEGED AND CONFIDENTIAL COMMUNICATION This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

[thetalkingdrum]

No worries:) Yes, I got them. Have to fire up my windows box to see if i can reproduce it. It seems like your screenshots did not come through, you will likely have to paste them directly in the github webpage, not by replying through email.

[aviduser1]

Hi Mats, something strange happened just now. My Windows Security detected a trojan virus all of a sudden and asked me to let it scan the machine and quarantine the virus. And now I realize NegPy has disappeared and also the icon to launch on the desktop is gone. Looks like Windows Security deleted NegPy altogether from my desktop and app tray. Obviously, it detected a Trojan virus in NegPy which was open all day. Do you know what that is about? This is seriously strange!!!

…

On Sun, Aug 30, 2026 at 1:55 AM thetalkingdrum ***@***.***> wrote: No worries:) Yes, I got them. Have to fire up my windows box to see if i can reproduce it. It seems like your screenshots did not come through, you will likely have to paste them directly in the github webpage, not by replying through email. — Reply to this email directly, view it on GitHub <#990?email_source=notifications&email_token=B2ZMGVH5NHI465DVRVBXFET5MPTY3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGA2TEOJSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18205292>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B2ZMGVA2N64ZIW5I6WYC7535MPTY3AVCNFSNUABJKJSXA33TNF2G64TZHMYTCMRTG43DMNRQHE5UI2LTMN2XG43JN5XDWMJQG4YDGOBZHGQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/B2ZMGVAH6ZKUHFJ4SO3JSC35MPTY3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGA2TEOJSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/B2ZMGVEWZHO4O5ZZWH6RVUD5MPTY3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGA2TEOJSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

-- -------------------------------------------------------------- PRIVILEGED AND CONFIDENTIAL COMMUNICATION This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

[thetalkingdrum]

Hi Avi, this sounds very much like it could be a Windows Defender false positive. NegPy is unsigned, relatively uncommon application. Defenders heuristic/ML detection can sometimes flag these executables unexpectedly. There has been some earlier reports as well of defender suddenly reporting Negpy.

The most useful thing would be to check Windows Security → Protection history and see the exact Trojan/detection name. If you post that here, it should be possible to determine whether it's a known false-positive pattern.

[aviduser1]

Never mind my last message. I think whatever was changed this morning in the update, Windows thought it was a threat and threw up a false positive. I checked the quarantine folder and it was indeed NegPy sitting in there with a Wacatac.C!ml, so I released it from quarantine and it is back on the desktop. Sorry to alarm you.

…

On Sun, Aug 30, 2026 at 1:55 AM thetalkingdrum ***@***.***> wrote: No worries:) Yes, I got them. Have to fire up my windows box to see if i can reproduce it. It seems like your screenshots did not come through, you will likely have to paste them directly in the github webpage, not by replying through email. — Reply to this email directly, view it on GitHub <#990?email_source=notifications&email_token=B2ZMGVH5NHI465DVRVBXFET5MPTY3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGA2TEOJSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18205292>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B2ZMGVA2N64ZIW5I6WYC7535MPTY3AVCNFSNUABJKJSXA33TNF2G64TZHMYTCMRTG43DMNRQHE5UI2LTMN2XG43JN5XDWMJQG4YDGOBZHGQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/B2ZMGVAH6ZKUHFJ4SO3JSC35MPTY3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGA2TEOJSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/B2ZMGVEWZHO4O5ZZWH6RVUD5MPTY3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBSGA2TEOJSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

-- -------------------------------------------------------------- PRIVILEGED AND CONFIDENTIAL COMMUNICATION This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

[aviduser1]

Hi Mats First off, I am really enjoying working with NegPy more and more, and it gets even better with every version. Thanks to the awesome development team. I have a question about a feature that I can use. Most of it is already there, just needs a boost. I put it on the Github page a few days ago. It is mainly this: I am using the Dodge and Burn tool inside of NegPy and liking it a lot. The way the tool is designed, I can turn off visibility of the Oval, Draw Mask and Card Edge, which is great! However, it would also be very helpful to have a way to suppress any or all of the effects of dodge and burn to be able to see and judge the image with and without the effects of Dodge and Burn. Right now, there is no way other than to delete the particular mask to see the image without the effect. Is it possible that we could click on the little icons at the front of the mask names to deactivate/activate the effect? All in all, the Dodge and Burn usage in NegPy feels a lot like using the Power Windows in DaVinci Resolve, another well thought out program. Adding this feature to the NegPy's Dodge and Burn module will be so fantastic, in my personal opinion! You may have seen my submission on Github as a Feature Request, if not, this is the one: #1059 Many thanks Avi

…

-- -------------------------------------------------------------- PRIVILEGED AND CONFIDENTIAL COMMUNICATION This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

[thetalkingdrum]

Hey Avi! I looked at it your request now and it seems like a good idea to add that as an improvement. I think several of the regular contributors might have had other stuff taking up their time the past few weeks, so things have been piling up a bit.

[aviduser1]

Hey Mats, thanks for responding. No worries! This feature in Dodge and Burn can wait, but would be great to have as I am using it more and more with my scans. BTW, when I try to add my own suffix to a file name in the Export section, somehow it does weird stuff, like it will jump letters and go to the very end of the line. I can't imagine that is normal behavior. For example: I am trying to name it - NikonFE_GA_VanNuys{{ original_name }}_FLAT_frm14 and what it does is - NikonFE_GA_VanNuys{{ original_name }}_Ffrm14LAT <--- you can see what happened in the added suffix in RED. FLAT got separated around frm14. I have to forcibly correct it. Am I doing something wrong? I am using NegPy on Windows 11, if that matters. And it doesn't matter how long the name is, it does it at the end part of the name. I have inadvertently named dozens of files weirdly like that by not checking. You should be able to reproduce the problem easily on a Windows machine if you want to. Thanks and have a great weekend Avi [image: NegPy_Screenshot_02.jpg]

…

On Sat, Sep 12, 2026 at 12:24 AM thetalkingdrum ***@***.***> wrote: Hey Avi! I looked at it your request now and it seems like a good idea to add that as an improvement. I think several of the regular contributors might have had other stuff taking up their time the past few weeks, so things have been piling up a bit. — Reply to this email directly, view it on GitHub <#990?email_source=notifications&email_token=B2ZMGVHLSGIP47S3V2UKVT35OT2Z3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGEYDCMZYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18410138>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B2ZMGVGDGL4R54EWSED75A35OT2Z3AVCNFSNUABJKJSXA33TNF2G64TZHMYTCMRTG43DMNRQHE5UI2LTMN2XG43JN5XDWMJQG4YDGOBZHGQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/B2ZMGVESUJPQEPT6CVFK3ID5OT2Z3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGEYDCMZYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/B2ZMGVGAFUYLQNPZ7O4PBQL5OT2Z3A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGEYDCMZYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

-- -------------------------------------------------------------- PRIVILEGED AND CONFIDENTIAL COMMUNICATION This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

[thetalkingdrum]

did you mean to include a screenshot here? It got lost. I think you need to use the web interface to upload images successfully.

[thetalkingdrum]

I think your file name bug was fixed here: #1075

[aviduser1]

Oops, I forgot about that. It was a screenshot showing the strange way the name gets written during export, which I explained in the message body. I am away from my machine for the night. Maybe I will post it on GitHub tomorrow. Thanks.

…

-------------------------------------------------------------- PRIVILEGED AND CONFIDENTIAL COMMUNICATION This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

On Sun, Sep 13, 2026, 3:38 AM thetalkingdrum ***@***.***> wrote: did you mean to include a screenshot here? It got lost. I think you need to use the web interface to upload images successfully. — Reply to this email directly, view it on GitHub <#990?email_source=notifications&email_token=B2ZMGVEYMC2A7LRJCAIJTPT5OZ2LFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGIYDINZUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18420474>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B2ZMGVFNAF4AVFSK5OL4I7T5OZ2LFAVCNFSNUABJKJSXA33TNF2G64TZHMYTCMRTG43DMNRQHE5UI2LTMN2XG43JN5XDWMJQG4YDGOBZHGQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/B2ZMGVFMR26IAVJJ5DRGWLT5OZ2LFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGIYDINZUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/B2ZMGVEAF72OSMPTYWCYTAT5OZ2LFA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGIYDINZUUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[aviduser1]

Thanks, I just tried it out and it works flawlessly!

…

On Mon, Sep 14, 2026 at 10:42 AM thetalkingdrum ***@***.***> wrote: I think you file name bug was fixed here: #1075 <#1075> — Reply to this email directly, view it on GitHub <#990?email_source=notifications&email_token=B2ZMGVFRG52OX3VWNHBRGIT5PAUXZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGM3TOOBSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18437782>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B2ZMGVH6RUFF3SBG4HWRF5T5PAUXZAVCNFSNUABJKJSXA33TNF2G64TZHMYTCMRTG43DMNRQHE5UI2LTMN2XG43JN5XDWMJQG4YDGOBZHGQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/B2ZMGVCAA72TSZND7NBX6V35PAUXZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGM3TOOBSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/B2ZMGVB43NVAPWQY6ACHDQL5PAUXZA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGM3TOOBSUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

-- -------------------------------------------------------------- PRIVILEGED AND CONFIDENTIAL COMMUNICATION This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.