Romuald Conty
Romuald Conty
Please note that development version and archives differs on this point : tarball do embedded all files generated by "autoreconf -is"
@Raskil As you are a user of `bump` feature, could you contribute to the discussion started at #216
What are the users opinion?
Could someone describe a real-life example where its useful to use a pre commit hook in `msync` context? This way, we can write a behavior test and fix this issue...
Regarding our discussion about lightweight of the `msync`, is this pre hook commit is not an overkill feature if we have an `exec` and `push` atomic command? If pre commit...
Thinking about this, I purpose a solution that looks better to me: What about allowing user to specify hooks in configuration files? Details: I think we could implement a way...
`exec` is a new feature without explicit behavior expected, but the most important thing to me during development was to keep some kind of _idempotency_ / _reproductibility_. ie. Running the...
I agree. Just for the story, I started to work on an `execute` command for `msync` first (see #199)... Even this #199 PR code is working and used by us...
Under Debian 12, a system-wide workaround could be to add `/usr/lib/ruby/3.1.0/openssl/ssl.rb` at line 29 this line: ```ruby opts |= OpenSSL::SSL::OP_IGNORE_UNEXPECTED_EOF ``` so the block looks like: ```ruby module OpenSSL module...
> I don't think that's a wise choice. I totally agree with you. I have no accesses to this kind of setup right now to test your suggestion but that...