Message ID | pull.1128.git.1643186507.gitgitgadget@gmail.com (mailing list archive) |
---|---|
Headers | show |
Series | scalar: implement the subcommand "diagnose" | expand |
On 1/26/2022 3:41 AM, Johannes Schindelin via GitGitGadget wrote: > Over the course of the years, we developed a sub-command that gathers > diagnostic data into a .zip file that can then be attached to bug reports. > This sub-command turned out to be very useful in helping Scalar developers > identify and fix issues. For historical context: The 'diagnose' command was implemented in VFS for Git and ported to the C# version of Scalar before 'git bugreport' existed, but they serve very similar purposes. I wonder if 'scalar diagnose' could include some of the information captured by 'git bugreport' or whether this implementation of 'diagnose' could help inform 'git bugreport' in any way. CC'ing Emily for thoughts. Thanks, -Stolee
Hi Stolee & Emily, On Thu, 27 Jan 2022, Derrick Stolee wrote: > On 1/26/2022 3:41 AM, Johannes Schindelin via GitGitGadget wrote: > > Over the course of the years, we developed a sub-command that gathers > > diagnostic data into a .zip file that can then be attached to bug reports. > > This sub-command turned out to be very useful in helping Scalar developers > > identify and fix issues. > > For historical context: The 'diagnose' command was implemented in VFS for > Git and ported to the C# version of Scalar before 'git bugreport' existed, > but they serve very similar purposes. > > I wonder if 'scalar diagnose' could include some of the information > captured by 'git bugreport' or whether this implementation of 'diagnose' > could help inform 'git bugreport' in any way. Indeed, I think that the `bugreport` command could easily benefit from at least the number of pack files and loose objects. Ciao, Dscho > > CC'ing Emily for thoughts. > > Thanks, > -Stolee >