{"thread":{"id":"63841","subject":"[ANN] git-phoenix - repository recovery tool","startedAt":"2025-07-24T18:49:52Z","lastAt":"2025-07-25T21:27:52Z","messageCount":5,"participants":["Daniil Iaitskov","Christian Couder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"522700","messageId":"f4b40536-346f-45a1-84ee-99b1200c022b@gmail.com","threadId":"63841","inReplyTo":null,"subject":"[ANN] git-phoenix - repository recovery tool","fromName":"Daniil Iaitskov","fromEmail":"dyaitskov@gmail.com","sentAt":"2025-07-24T18:49:50Z","receivedAt":"2025-07-24T18:49:52Z","isPatch":false,"sender":{"key":"dyaitskov@gmail.com","avatar":"https://gravatar.com/avatar/8d94c1b07247d73c1846ae3b6b7d4632e5f9ce97df3c69384fef7295a0ee172b?d=mp&s=160"},"body":"Hi Git List,\n\nI would like to share a tool for recovery an unpublished Git repository \nafter accidental removal or file system failure. VCS usually implies \nbackup feature auto of the box, but due to Git decentralized nature and \ndeveloper's laziness source code sometimes can be lost. Recently I \naccidentally deleted all projects, including a few unpulished POCs, \nafter infamous rm -rf * typo. Work on them has been interrupted for \nquite awhile and rewriting them from scratch recalling all the hack \nintricacies would be terribly boring. So I decided to invest my dev time \nin a more creative way.\n\nhttps://github.com/yaitskov/git-phoenix/\n\n\nBest regards,\n\nDaniil Iaitskov\n"},{"id":"522762","messageId":"CAP8UFD10KuuM8Xu5YDxDf+rzN5r0TxgOw=do94dPO51hOCyE1w@mail.gmail.com","threadId":"63841","inReplyTo":"f4b40536-346f-45a1-84ee-99b1200c022b@gmail.com","subject":"Re: [ANN] git-phoenix - repository recovery tool","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2025-07-25T18:12:43Z","receivedAt":"2025-07-25T18:12:56Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"Hi Daniil,\n\nOn Thu, Jul 24, 2025 at 8:49 PM Daniil Iaitskov wrote:\n>\n> Hi Git List,\n>\n> I would like to share a tool for recovery an unpublished Git repository\n> after accidental removal or file system failure. VCS usually implies\n> backup feature auto of the box, but due to Git decentralized nature and\n> developer's laziness source code sometimes can be lost. Recently I\n> accidentally deleted all projects, including a few unpulished POCs,\n> after infamous rm -rf * typo. Work on them has been interrupted for\n> quite awhile and rewriting them from scratch recalling all the hack\n> intricacies would be terribly boring. So I decided to invest my dev time\n> in a more creative way.\n>\n> https://github.com/yaitskov/git-phoenix/\n\nThanks for creating it. It doesn't seem to have a license, which might\nprevent some of us from using it, though.\n\nAnyway for now there is the following pull request to talk about it in\nthe next Git Rev News edition:\n\nhttps://github.com/git/git.github.io/pull/790\n\nBest,\nChristian.\n"},{"id":"522763","messageId":"fe5d1d5e-15fe-4d00-96c4-d5a4a3b568c5@gmail.com","threadId":"63841","inReplyTo":"CAP8UFD10KuuM8Xu5YDxDf+rzN5r0TxgOw=do94dPO51hOCyE1w@mail.gmail.com","subject":"Re: [ANN] git-phoenix - repository recovery tool","fromName":"Daniil Iaitskov","fromEmail":"dyaitskov@gmail.com","sentAt":"2025-07-25T18:40:56Z","receivedAt":"2025-07-25T18:40:59Z","isPatch":false,"sender":{"key":"dyaitskov@gmail.com","avatar":"https://gravatar.com/avatar/8d94c1b07247d73c1846ae3b6b7d4632e5f9ce97df3c69384fef7295a0ee172b?d=mp&s=160"},"body":"\n\nOn 7/25/25 10:12, Christian Couder wrote:\n> Hi Daniil,\n> \n> On Thu, Jul 24, 2025 at 8:49 PM Daniil Iaitskov wrote:\n>>\n>> Hi Git List,\n>>\n>> I would like to share a tool for recovery an unpublished Git repository\n>> after accidental removal or file system failure. VCS usually implies\n>> backup feature auto of the box, but due to Git decentralized nature and\n>> developer's laziness source code sometimes can be lost. Recently I\n>> accidentally deleted all projects, including a few unpulished POCs,\n>> after infamous rm -rf * typo. Work on them has been interrupted for\n>> quite awhile and rewriting them from scratch recalling all the hack\n>> intricacies would be terribly boring. So I decided to invest my dev time\n>> in a more creative way.\n>>\n>> https://github.com/yaitskov/git-phoenix/\n> \n> Thanks for creating it. It doesn't seem to have a license, which might\n> prevent some of us from using it, though.\n\nLicense is specified in project file (BSD3):\nhttps://github.com/yaitskov/git-phoenix/blob/9a88c55fd45f28d4e1865df3ac746b409474eaf7/git-phoenix.cabal#L135\n\nThe tool is also published on hackage under BSD3:\nhttps://hackage.haskell.org/package/git-phoenix-0.0.2\n\nI don't see much difference between open source licenses and picked BSD3 \njust because it is popular here.\n\nWhat license would like to see?\n\n> \n> Anyway for now there is the following pull request to talk about it in\n> the next Git Rev News edition:\n> \n> https://github.com/git/git.github.io/pull/790\n> \n> Best,\n> Christian.\n\nBest regards,\nDaniil Iaitskov\n\n"},{"id":"522766","messageId":"CAP8UFD19rjmOYR2KZ6qBM2zWMaNJknSdwbOijMRVn-RQoejezA@mail.gmail.com","threadId":"63841","inReplyTo":"fe5d1d5e-15fe-4d00-96c4-d5a4a3b568c5@gmail.com","subject":"Re: [ANN] git-phoenix - repository recovery tool","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2025-07-25T19:01:29Z","receivedAt":"2025-07-25T19:01:43Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Fri, Jul 25, 2025 at 8:40 PM Daniil Iaitskov wrote:\n>\n> On 7/25/25 10:12, Christian Couder wrote:\n\n> > Thanks for creating it. It doesn't seem to have a license, which might\n> > prevent some of us from using it, though.\n>\n> License is specified in project file (BSD3):\n> https://github.com/yaitskov/git-phoenix/blob/9a88c55fd45f28d4e1865df3ac746b409474eaf7/git-phoenix.cabal#L135\n\nOk, I just saw that GitHub didn't display the license information at\nthe top of your repository page, and then only took a look at the\nREADME where I couldn't find any license information.\n\nIt seems that you need to add a file named LICENSE (or LICENSE.txt,\nLICENSE.md) with the full text of your chosen license in the root\ndirectory of your repository for GitHub to automatically detect and\ndisplay it. I could help people find that information and be more\nconfident that they can use it.\n\n> The tool is also published on hackage under BSD3:\n> https://hackage.haskell.org/package/git-phoenix-0.0.2\n>\n> I don't see much difference between open source licenses and picked BSD3\n> just because it is popular here.\n>\n> What license would like to see?\n\nIt's your choice and I don't have any say in it, but I am happy that\nit is open source :-)\n\nThanks.\n"},{"id":"522773","messageId":"d30839d8-35a2-4670-8f0e-663cf8fbee3c@gmail.com","threadId":"63841","inReplyTo":"CAP8UFD19rjmOYR2KZ6qBM2zWMaNJknSdwbOijMRVn-RQoejezA@mail.gmail.com","subject":"Re: [ANN] git-phoenix - repository recovery tool","fromName":"Daniil Iaitskov","fromEmail":"dyaitskov@gmail.com","sentAt":"2025-07-25T21:27:49Z","receivedAt":"2025-07-25T21:27:52Z","isPatch":false,"sender":{"key":"dyaitskov@gmail.com","avatar":"https://gravatar.com/avatar/8d94c1b07247d73c1846ae3b6b7d4632e5f9ce97df3c69384fef7295a0ee172b?d=mp&s=160"},"body":"\n\nOn 7/25/25 11:01, Christian Couder wrote:\n> On Fri, Jul 25, 2025 at 8:40 PM Daniil Iaitskov wrote:\n>>\n>> On 7/25/25 10:12, Christian Couder wrote:\n> \n>>> Thanks for creating it. It doesn't seem to have a license, which might\n>>> prevent some of us from using it, though.\n>>\n>> License is specified in project file (BSD3):\n>> https://github.com/yaitskov/git-phoenix/blob/9a88c55fd45f28d4e1865df3ac746b409474eaf7/git-phoenix.cabal#L135\n> \n> Ok, I just saw that GitHub didn't display the license information at\n> the top of your repository page, and then only took a look at the\n> README where I couldn't find any license information.\n> \n> It seems that you need to add a file named LICENSE (or LICENSE.txt,\n> LICENSE.md) with the full text of your chosen license in the root\n> directory of your repository for GitHub to automatically detect and\n> display it. I could help people find that information and be more\n> confident that they can use it.\n\nThanks for feedback.\nAfter getting familiar with content of a few BSD3 license files\nI was able to commit mine.\n\n\n> \n>> The tool is also published on hackage under BSD3:\n>> https://hackage.haskell.org/package/git-phoenix-0.0.2\n>>\n>> I don't see much difference between open source licenses and picked BSD3\n>> just because it is popular here.\n>>\n>> What license would like to see?\n> \n> It's your choice and I don't have any say in it, but I am happy that\n> it is open source :-)\n> \n> Thanks.\n\n"}]}