[Octave-bug-tracker] [bug #64760] VM Make VM runnable on 32 bit systems

[Markus Mützel]

Follow-up Comment #6, bug #64760 (project octave):

That might be a weak argument. But sometimes I find these "keywords" helpful
when scanning through a range of commits (to try and "visually bisect"
quickly). E.g., if something in the interpreter failed, it's likely not one of
the commits that start with "doc:" or "gui:".
On the other hand, if something changed only when using the vm evaluator, it's
more likely that one of the commits starting with "vm:" is the one to
inspect.
If "configure" breaks or gives incorrect results, it's likely one of the
commits starting with "build:" that might have caused it.
That's assuming that the commits are categorized "correctly".

"libgui" is a separate library. So, categorizing changes for it is pretty
clear cut (and maybe could also be filtered by path). For other parts, that
might be less obvious.

There might also be developers that have their main focus on only parts of
Octave's code base. For those, these keywords could also be useful.
If you prefer to not use these keywords, or use a different set of keywords
that's fine with me.

What do you have in mind?




    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64760>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/