https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
--- Comment #69 from Franco Fichtner ---
(In reply to Dag-Erling Smørgrav from comment #68)
Thank you for participating. You may want to read comment 57 first.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
Dag-Erling Smørgrav changed:
What|Removed |Added
CC||d...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280036
Konstantin Belousov changed:
What|Removed |Added
CC||k...@freebsd.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281211
--- Comment #3 from Stas Alekseev ---
I have submitted a path with potential fix at
https://github.com/freebsd/freebsd-src/pull/1408
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281211
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
--- Comment #67 from Franco Fichtner ---
There are some open release engineering questions in this thread, lack of
professionalism discarding a problem that was later fixed without comment
aside. Doing the least bit of rectifying the previo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
--- Comment #66 from doktornotor ---
(In reply to Gordon Tetlow from comment #65)
I'm afraid the point was sort of missed here. What I meant by "more
communication" is that whoever committed the buggy code should not maintain
radio silenc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280701
--- Comment #65 from Gordon Tetlow ---
In reply to doktornotor from comment #64:
> Not sure about other people here suffering from the regressions, but I'd
> seriously appreciate some form of communication beyond automated
> commit-hook@ me
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233683
Mark Johnston changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progre
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280705
--- Comment #14 from commit-h...@freebsd.org ---
A commit in branch stable/14 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=8ae58e0edbfb4c56125fb6d7468ebfea638847b9
commit 8ae58e0edbfb4c56125fb6d7468ebfea638847b9
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280036
--- Comment #10 from Marek Zarychta ---
While investigating the bug, I found that when ftpd(8) is serving a file from
the OpenVPN access server itself (from the ZFS filesystem in my case), the file
silently (apparently!) gets corrupted on t
11 matches
Mail list logo