{"thread":{"id":"65705","subject":"","startedAt":"2026-05-28T05:08:10Z","lastAt":"2026-05-28T14:16:39Z","messageCount":2,"participants":["胡锦","Weijie Yuan"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"544207","messageId":"tencent_124443E95FD3502A16815464@qq.com","threadId":"65705","inReplyTo":null,"subject":"","fromName":"胡锦","fromEmail":"hujin2@sunline.cn","sentAt":"2026-05-28T05:08:05Z","receivedAt":"2026-05-28T05:08:10Z","isPatch":false,"body":"Dear Git Team,\n\nMy name is Hujin, and I am an IT engineer from China. I have been using Git for more than 10 years.\n\nFirst of all, I would like to express my appreciation for Git. In my experience, Git remains one of the best and most reliable version control systems in modern software development. It has played an important role in many projects I have worked on.\n\nHowever, I have also encountered a recurring difficulty in daily use. For certain types of files, especially files under script directories or other frequently modified directories, conflicts happen quite often because updates are not synchronized in real time. In some project scenarios, multiple engineers may edit related scripts at the same time, and this can lead to repeated merge conflicts and extra coordination costs.\n\nI wonder whether Git could provide, in future versions, some optional features similar to online collaborative documents, or directory-level collaboration mechanisms for specific files or folders. For example, users could enable special real-time update, lock, notification, or conflict-reduction behavior for selected directories such as scripts. This could help reduce conflicts and make Git even more convenient for teams working on highly shared files.\n\nI understand that Git is designed as a distributed version control system, and such functionality may not be simple to implement. Still, I believe an optional feature in this direction could be very helpful for many engineering teams.\n\nThank you for your great work on Git. I look forward to hearing your thoughts.\n\nBest regards,Hujin"},{"id":"544227","messageId":"ahhOLaHJByKzVnGV@wyuan.org","threadId":"65705","inReplyTo":"tencent_124443E95FD3502A16815464@qq.com","subject":"Re:","fromName":"Weijie Yuan","fromEmail":"wy@wyuan.org","sentAt":"2026-05-28T14:16:13Z","receivedAt":"2026-05-28T14:16:39Z","isPatch":false,"body":"Hi,\n\nI'm just a diver here, but I would like to give you some suggestions though.\n\n* Your email doesn't have a subject line. So it seems not possible for\n  a true dev here to be interested in your email.\n\n* I guess you would need a proper text editor or a proper email client,\n  your email doen's wrap perfectly.\n\nAs for your feature request, I believe it's even harder, as for the \"online\ncollaborative documents\". This doesn't seem like a problem that git was\ndesigned to solve, but more like features of certain forges. Based on\ndiscussions in recent years, this feature you are looking for is not\nwithin the scope or schedule of discussion.\n\nBut I guess they would be more possible to discuss it if you could\nattach some patches.\n\nThanks.\n"}]}