Shea690901

Hmmm... For me it's more logical as is: You need the hotfix merged into develop for new feature branches.... Of course, you might need to rebase your feature branch on...

Since it's not with certainty that the hotfix would be needed within the new release that would be the best bet... Although one has to expect that the hotfix won't...

As I see it, support branches are for LTS versions. You might (hot|bug)fix the current release within the master branch, but you also have some LTS versions which are (hot|bug)fixed...

I propose a `git flow cleanup` that walks over those entries and removes them from the config file if the corresponding branches no longer exist...

According to 'vm/internal/base/interpret.cc' line 1317/1320, local variables are initialized as `const0u` meaning: undefined ;) Consequence: you might return an undefined value by returning a local variable which never got ahything...

I agree with you on the point of an 'undef' keyword and also the way it should be implemented… But that still doesn't explain your reasoning to return 0 for...

Ok! But that's not exactly a change of api, is it? The api documentation clearly states thatnthe signature of both functions is string->string and 0 is clearly not a atring,...

@nagisa wrote: > I couldn't find any command that would take multiple files for one switch, so I used clang with multiple outputs (it doesn't). Auto-completed part is denoted by...

Sorry for the long delay, problems in setting up my new machine.... As I wrote: It might work accidently, but if all is working as expected, according the code, it...