| Age | Commit message (Collapse) | Author |
|---|
|
- if the soft line length limit was breached and braking the line
failed and the buffer had already reached a certain size a
hard line length limit breached error was triggered (but should
not have)
|
|
- We want to eat ws if we do a linebreake at a place where we
did a write_fws().
- But we don't want to do so if we just did a `mark_fws_pos()`
|
|
|
|
The function for efficiently inserting a slice of bytes into
a `Vec<u8>` did miss a bounds check and was, to make thinks
worse optimized using unsafe code. Still the bug was only
latent as all parts using the function allways had in bounds
indexes. (There was only one, which was in a grow only buffer
and used a index which is always set from the current buffer
len, which as noted can only grow).
|
|
This is neccessary as `Any::get_type_id` is getting stabilized
as `Any::type_id` leading to potential brakage wrt. the compiler
failing due to syntax ambiguity.
|
|
|
|
|
|
Originally it was palaned to do a merge with `--allow-unrelated-history`
but this can not be doesn as `mail-core` has a "invalid" history which
has a merge conflict **with itself**. So even rewinding the history on
a empty repo is not possible.
Instead the code was directly coppied over losing history.
But the history is still available in the different
`history-backup-*` branches. It is just that the past history
is decoupled from the current history.
|
