Hi Ævar, On Thu, 30 Aug 2018, Ævar Arnfjörð Bjarmason wrote: > On Thu, Aug 30 2018, Johannes Schindelin wrote: > > > On Wed, 29 Aug 2018, Junio C Hamano wrote: > > > >> Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > >> > >> > The `stash` command only incidentally requires that the author is set, as > >> > it calls `git commit` internally (which records the author). As stashes > >> > are intended to be local only, that author information was never meant to > >> > be a vital part of the `stash`. > >> > > >> > I could imagine that an even better enhancement request would ask for `git > >> > stash` to work even if `user.name` is not configured. > >> > >> This would make a good bite-sized microproject, worth marking it as > >> #leftoverbits unless somebody is already working on it ;-) > > > > Right. > > > > What is our currently-favored approach to this, again? Do we have a > > favorite wiki page to list those, or do we have a bug tracker for such > > mini-projects? > > > > Once I know, I will add this, with enough information to get anybody > > interested started. > > I believe the "official" way, such as it is, is you just put > #leftoverbits in your E-Mail, then search the list archives, > e.g. https://public-inbox.org/git/?q=%23leftoverbits > > So e.g. I've taken to putting this in my own E-Mails where I spot > something I'd like to note as a TODO that I (or someone else) could work > on later: > https://public-inbox.org/git/?q=%23leftoverbits+f%3Aavarab%40gmail.com That is a poor way to list the current micro-projects, as it is totally non-obvious to the casual interested person which projects are still relevant, and which ones have been addressed already. In a bug tracker, you can at least add a comment stating that something has been addressed, or made a lot easier by another topic. In a mailing list archive, those mails are immutable, and you cannot update squat. Ciao, Johannes
