Am Mi., 24. Apr. 2019 um 13:57 Uhr schrieb Michael Gratton <m...@vee.net>: > > On Wed, Apr 24, 2019 at 13:31, Daniel Mustieles García > <daniel.mustie...@gmail.com> wrote: > > So hardcoding the name "mainline" to the list of branches that Damned > > Lies' looks up resolves the problem for you... and tomorrow another > > maintainer decides to rename it's master branch to > > whatever_non_offensive_name and DL breaks again until a patch is > > submited... no, sorry but this is not a solution for this. > > I agree, which is why I have been working to fix it places where it's > hard coded.
When actually working on the project, you probably type the branch name now and then. This means you need to be aware of it - it is a piece of information which must reside within your short-term memory. This is not a problem if you work on one project. It is a problem if you work on hundreds of projects. Then you need to run things like git branch and git status, read the output, and decide what to type based on that. A good workflow seeks to minimize the risk that humans make mistakes, and that means making things as simple as possible. Please do not remove this particular piece of simplicity from our lives. I can also script my way out of this for most of the tasks I need to do. But inconsistencies have never made life easier in computing, and this is an inconsistency which we could simply choose not to deal with. Best regards Ask > > //Mike > > -- > ⊨ Michael Gratton, Percept Wrangler. > ⚙ <http://mjog.vee.net/> > > > _______________________________________________ > gnome-i18n mailing list > gnome-i18n@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-i18n _______________________________________________ gnome-i18n mailing list gnome-i18n@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-i18n
