{"thread":{"id":"55549","subject":"[feature suggestion] Improve stash descriptions","startedAt":"2021-04-23T21:16:42Z","lastAt":"2021-04-26T16:14:12Z","messageCount":4,"participants":["Yuri","brian m. carlson","Ævar Arnfjörð Bjarmason","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"422820","messageId":"ff84d047-c0ae-86d1-c210-b2b777fd8184@rawbw.com","threadId":"55549","inReplyTo":null,"subject":"[feature suggestion] Improve stash descriptions","fromName":"Yuri","fromEmail":"yuri@rawbw.com","sentAt":"2021-04-23T21:16:38Z","receivedAt":"2021-04-23T21:16:42Z","isPatch":false,"sender":{"key":"yuri@rawbw.com","avatar":null},"body":"My current stash looks like this:\n\n$ git stash list\nstash@{0}: WIP on main: 12c63aaa3b13 www/yt-dlp: Update 2021.04.11 -> \n2021.04.22 Reported by: portscout\nstash@{1}: WIP on main: 140f08246898 devel/py-PeachPy: Update g20180225 \n-> 0.0.1\nstash@{2}: WIP on main: d42e82e4a336 security/hs-cryptol: Update 2.10.0 \n-> 2.11.0\nstash@{3}: WIP on main: 62851ab415cd dns/subfinder: Update 2.4.6 -> 2.4.7\nstash@{4}: WIP on main: 4eec712dfdae math/gretl: Correct PKGNAME to be \n2021a, not 2021.a to reflect how Gretl is versioned.\nstash@{5}: WIP on main: 725e4e9a07f0 devel/py-fypp: Update 3.0 -> 3.1\nstash@{6}: WIP on main: 200eb286c368 misc/py-orange3-educational: Update \n0.1.8 -> 0.4.0\nstash@{7}: WIP on main: 364ab57861e2 misc/urh: Update 2.9.1 -> 2.9.2\nstash@{8}: WIP on main: 52c6d02708d0 science/py-nilearn: Update 0.7.0 -> \n0.7.1\nstash@{9}: WIP on main: a9d5d9e05bbf New port: biology/seqkit: \nCross-platform and ultrafast toolkit for FASTA/Q file manipulation\nstash@{10}: WIP on main: ffa307fb4dc3 games/iqpuzzle: Update 1.2.2 -> 1.2.3\nstash@{11}: WIP on main: 195f2e27fd72 math/py-libpoly: Update 0.1.8 -> 0.1.9\nstash@{12}: WIP on main: 4c2cc95952a6 graphics/mesa-devel: update to \n21.0.b.4390\nstash@{13}: WIP on main: 4c2cc95952a6 graphics/mesa-devel: update to \n21.0.b.4390\nstash@{14}: On main: audio/tuxguitar -- .\nstash@{15}: On main: math/[py-]python-igraph\n\nNone of the above descriptions are relevant to actual items, for example:\n\n$ git stash show stash@{2}\n  devel/google-perftools/Makefile                      |  2 +-\n  devel/google-perftools/distinfo                      |  6 +++---\n  devel/google-perftools/files/patch-Makefile.am       |  4 ++--\n  devel/google-perftools/files/patch-src_stacktrace.cc | 11 +++++++++++\n  devel/google-perftools/pkg-plist                     | 12 ++++++------\n  5 files changed, 23 insertions(+), 12 deletions(-)\n\n- description mentions cryptol but actual items are related to perftools.\n\n\nMy suggestion:\n\nIn case all changes are grouped in one ditectory, like in my case, git \nshould append this directory name to description:\n\n > stash@{2}: WIP on main: d42e82e4a336 security/hs-cryptol: Update \n2.10.0 -> 2.11.0, all changes are in devel/google-perftools\n\n\nIn many cases it is possible to do so.\n\nIn case many directories are affected it could say \"changes are in \npath1/dir1, path2/dir2, etc.\"\n\nThis would be a lot better than stash items descriptions it prints now.\n\n\nThank you,\n\nYuri\n\n"},{"id":"422894","messageId":"YIWkHBfb4g68Oxr3@camp.crustytoothpaste.net","threadId":"55549","inReplyTo":"ff84d047-c0ae-86d1-c210-b2b777fd8184@rawbw.com","subject":"Re: [feature suggestion] Improve stash descriptions","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2021-04-25T17:17:16Z","receivedAt":"2021-04-25T17:17:54Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On 2021-04-23 at 21:16:38, Yuri wrote:\n> My current stash looks like this:\n> \n> $ git stash list\n> stash@{0}: WIP on main: 12c63aaa3b13 www/yt-dlp: Update 2021.04.11 ->\n> 2021.04.22 Reported by: portscout\n> stash@{1}: WIP on main: 140f08246898 devel/py-PeachPy: Update g20180225 ->\n> 0.0.1\n> stash@{2}: WIP on main: d42e82e4a336 security/hs-cryptol: Update 2.10.0 ->\n> 2.11.0\n> stash@{3}: WIP on main: 62851ab415cd dns/subfinder: Update 2.4.6 -> 2.4.7\n> stash@{4}: WIP on main: 4eec712dfdae math/gretl: Correct PKGNAME to be\n> 2021a, not 2021.a to reflect how Gretl is versioned.\n> stash@{5}: WIP on main: 725e4e9a07f0 devel/py-fypp: Update 3.0 -> 3.1\n> stash@{6}: WIP on main: 200eb286c368 misc/py-orange3-educational: Update\n> 0.1.8 -> 0.4.0\n> stash@{7}: WIP on main: 364ab57861e2 misc/urh: Update 2.9.1 -> 2.9.2\n> stash@{8}: WIP on main: 52c6d02708d0 science/py-nilearn: Update 0.7.0 ->\n> 0.7.1\n> stash@{9}: WIP on main: a9d5d9e05bbf New port: biology/seqkit:\n> Cross-platform and ultrafast toolkit for FASTA/Q file manipulation\n> stash@{10}: WIP on main: ffa307fb4dc3 games/iqpuzzle: Update 1.2.2 -> 1.2.3\n> stash@{11}: WIP on main: 195f2e27fd72 math/py-libpoly: Update 0.1.8 -> 0.1.9\n> stash@{12}: WIP on main: 4c2cc95952a6 graphics/mesa-devel: update to\n> 21.0.b.4390\n> stash@{13}: WIP on main: 4c2cc95952a6 graphics/mesa-devel: update to\n> 21.0.b.4390\n> stash@{14}: On main: audio/tuxguitar -- .\n> stash@{15}: On main: math/[py-]python-igraph\n> \n> None of the above descriptions are relevant to actual items, for example:\n> \n> $ git stash show stash@{2}\n>  devel/google-perftools/Makefile                      |  2 +-\n>  devel/google-perftools/distinfo                      |  6 +++---\n>  devel/google-perftools/files/patch-Makefile.am       |  4 ++--\n>  devel/google-perftools/files/patch-src_stacktrace.cc | 11 +++++++++++\n>  devel/google-perftools/pkg-plist                     | 12 ++++++------\n>  5 files changed, 23 insertions(+), 12 deletions(-)\n> \n> - description mentions cryptol but actual items are related to perftools.\n\nRight.  The format here is \"WIP on BRANCH: REVISION DESCRIPTION\", where\nREVISION and DESCRIPTION correspond to the latest commit on the branch.\n\nI agree that in many situations this is an unhelpful message, which is\nwhy git stash push takes a --message argument so you can specify a\ndifferent message.  That, of course, does require that you use it, and\nI will admit that even I don't always do that, sometimes much to the\ndismay of later me.\n\n> In case all changes are grouped in one ditectory, like in my case, git\n> should append this directory name to description:\n> \n> > stash@{2}: WIP on main: d42e82e4a336 security/hs-cryptol: Update 2.10.0 ->\n> 2.11.0, all changes are in devel/google-perftools\n> \n> \n> In many cases it is possible to do so.\n> \n> In case many directories are affected it could say \"changes are in\n> path1/dir1, path2/dir2, etc.\"\n\nThis is unfortunately not going to be very efficient to compute in\ncertain cases, such as with large working trees where there are many\nchanges.  So while it would improve the automated stash message, it\nmight also make stashing much slower on large repositories.\n-- \nbrian m. carlson (he/him or they/them)\nHouston, Texas, US\n"},{"id":"422919","messageId":"87r1ix4dsc.fsf@evledraar.gmail.com","threadId":"55549","inReplyTo":"YIWkHBfb4g68Oxr3@camp.crustytoothpaste.net","subject":"Re: [feature suggestion] Improve stash descriptions","fromName":"Ævar Arnfjörð Bjarmason","fromEmail":"avarab@gmail.com","sentAt":"2021-04-26T09:00:57Z","receivedAt":"2021-04-26T09:04:56Z","isPatch":false,"sender":{"key":"avarab@gmail.com","avatar":"https://avatars.githubusercontent.com/u/45301?v=4"},"body":"\nOn Sun, Apr 25 2021, brian m. carlson wrote:\n\n> [[PGP Signed Part:Undecided]]\n> On 2021-04-23 at 21:16:38, Yuri wrote:\n>> My current stash looks like this:\n>> \n>> $ git stash list\n>> stash@{0}: WIP on main: 12c63aaa3b13 www/yt-dlp: Update 2021.04.11 ->\n>> 2021.04.22 Reported by: portscout\n>> stash@{1}: WIP on main: 140f08246898 devel/py-PeachPy: Update g20180225 ->\n>> 0.0.1\n>> stash@{2}: WIP on main: d42e82e4a336 security/hs-cryptol: Update 2.10.0 ->\n>> 2.11.0\n>> stash@{3}: WIP on main: 62851ab415cd dns/subfinder: Update 2.4.6 -> 2.4.7\n>> stash@{4}: WIP on main: 4eec712dfdae math/gretl: Correct PKGNAME to be\n>> 2021a, not 2021.a to reflect how Gretl is versioned.\n>> stash@{5}: WIP on main: 725e4e9a07f0 devel/py-fypp: Update 3.0 -> 3.1\n>> stash@{6}: WIP on main: 200eb286c368 misc/py-orange3-educational: Update\n>> 0.1.8 -> 0.4.0\n>> stash@{7}: WIP on main: 364ab57861e2 misc/urh: Update 2.9.1 -> 2.9.2\n>> stash@{8}: WIP on main: 52c6d02708d0 science/py-nilearn: Update 0.7.0 ->\n>> 0.7.1\n>> stash@{9}: WIP on main: a9d5d9e05bbf New port: biology/seqkit:\n>> Cross-platform and ultrafast toolkit for FASTA/Q file manipulation\n>> stash@{10}: WIP on main: ffa307fb4dc3 games/iqpuzzle: Update 1.2.2 -> 1.2.3\n>> stash@{11}: WIP on main: 195f2e27fd72 math/py-libpoly: Update 0.1.8 -> 0.1.9\n>> stash@{12}: WIP on main: 4c2cc95952a6 graphics/mesa-devel: update to\n>> 21.0.b.4390\n>> stash@{13}: WIP on main: 4c2cc95952a6 graphics/mesa-devel: update to\n>> 21.0.b.4390\n>> stash@{14}: On main: audio/tuxguitar -- .\n>> stash@{15}: On main: math/[py-]python-igraph\n>> \n>> None of the above descriptions are relevant to actual items, for example:\n>> \n>> $ git stash show stash@{2}\n>>  devel/google-perftools/Makefile                      |  2 +-\n>>  devel/google-perftools/distinfo                      |  6 +++---\n>>  devel/google-perftools/files/patch-Makefile.am       |  4 ++--\n>>  devel/google-perftools/files/patch-src_stacktrace.cc | 11 +++++++++++\n>>  devel/google-perftools/pkg-plist                     | 12 ++++++------\n>>  5 files changed, 23 insertions(+), 12 deletions(-)\n>> \n>> - description mentions cryptol but actual items are related to perftools.\n>\n> Right.  The format here is \"WIP on BRANCH: REVISION DESCRIPTION\", where\n> REVISION and DESCRIPTION correspond to the latest commit on the branch.\n>\n> I agree that in many situations this is an unhelpful message, which is\n> why git stash push takes a --message argument so you can specify a\n> different message.  That, of course, does require that you use it, and\n> I will admit that even I don't always do that, sometimes much to the\n> dismay of later me.\n>\n>> In case all changes are grouped in one ditectory, like in my case, git\n>> should append this directory name to description:\n>> \n>> > stash@{2}: WIP on main: d42e82e4a336 security/hs-cryptol: Update 2.10.0 ->\n>> 2.11.0, all changes are in devel/google-perftools\n>> \n>> \n>> In many cases it is possible to do so.\n>> \n>> In case many directories are affected it could say \"changes are in\n>> path1/dir1, path2/dir2, etc.\"\n>\n> This is unfortunately not going to be very efficient to compute in\n> certain cases, such as with large working trees where there are many\n> changes.  So while it would improve the automated stash message, it\n> might also make stashing much slower on large repositories.\n\nJust to add to this, there's already:\n\n    git stash list [--stat|--numstat|--shortstat]\n\nIt seems to me that what's being requested here is not so much a\nstash-specific feature, but some abbreviated \"human readable\" stat\nformat that could be used with any log-like command.\n"},{"id":"422941","messageId":"YIbmz2BUKV0/pcIB@coredump.intra.peff.net","threadId":"55549","inReplyTo":"87r1ix4dsc.fsf@evledraar.gmail.com","subject":"Re: [feature suggestion] Improve stash descriptions","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2021-04-26T16:14:07Z","receivedAt":"2021-04-26T16:14:12Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Apr 26, 2021 at 11:00:57AM +0200, Ævar Arnfjörð Bjarmason wrote:\n\n> >> In case many directories are affected it could say \"changes are in\n> >> path1/dir1, path2/dir2, etc.\"\n> >\n> > This is unfortunately not going to be very efficient to compute in\n> > certain cases, such as with large working trees where there are many\n> > changes.  So while it would improve the automated stash message, it\n> > might also make stashing much slower on large repositories.\n> \n> Just to add to this, there's already:\n> \n>     git stash list [--stat|--numstat|--shortstat]\n> \n> It seems to me that what's being requested here is not so much a\n> stash-specific feature, but some abbreviated \"human readable\" stat\n> format that could be used with any log-like command.\n\nThere's also --dirstat, which will summarize the impacted directories\n(though it does not say much useful if the entries are all in the root,\nas they typically are for git.git).\n\n-Peff\n"}]}