https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
Ed Maste changed:
What|Removed |Added
Resolution|--- |FIXED
Status|In Progress
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
--- Comment #11 from commit-h...@freebsd.org ---
A commit in branch stable/12 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=bb727917364f7ded1d24f599389288c63b23d862
commit bb727917364f7ded1d24f599389288c63b23d862
Author
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
--- Comment #10 from Ed Maste ---
(In reply to Graham Perrin from comment #9)
It wouldn't hurt, but also is probably not going to be that useful to people
upgrading *to* 13.2, who are upgrading *from* a FreeBSD version where
freebsd-update
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
--- Comment #9 from Graham Perrin ---
(In reply to commit-hook from comment #8)
Should we have a 13.2 release note for
a6c6edbe9d37caf1dbc81f918adf8c1f451a534e?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
--- Comment #8 from commit-h...@freebsd.org ---
A commit in branch releng/13.2 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=a6c6edbe9d37caf1dbc81f918adf8c1f451a534e
commit a6c6edbe9d37caf1dbc81f918adf8c1f451a534e
Autho
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
--- Comment #7 from commit-h...@freebsd.org ---
A commit in branch stable/13 references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=c7e3703352037a5afacdc4126725f351fe7da72b
commit c7e3703352037a5afacdc4126725f351fe7da72b
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
Ed Maste changed:
What|Removed |Added
Status|Open|In Progress
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
--- Comment #6 from commit-h...@freebsd.org ---
A commit in branch main references this bug:
URL:
https://cgit.FreeBSD.org/src/commit/?id=ceb5f28ba5fcfa69de7410d2327d4a5abf2a421f
commit ceb5f28ba5fcfa69de7410d2327d4a5abf2a421f
Author:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
Graham Perrin changed:
What|Removed |Added
See Also||https://reviews.freebsd.org
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
--- Comment #4 from Ed Maste ---
(In reply to Graham Perrin from comment #2)
Prefixing the conflict markers with a comment character (#) isn't viable - it
could result in even more confusing or unclear behaviour, as the config file
would en
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
See Also|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
--- Comment #3 from Graham Perrin ---
(In reply to Dan MacDonald from comment #0)
> … tired or in a hurry … blindly accepted …
Somewhat off-topic:
* might oversight (blind acceptance) have been less likely if
something other than vi
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
Graham Perrin changed:
What|Removed |Added
CC||grahamper...@gmail.com
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
Thanos changed:
What|Removed |Added
CC||arkr17...@gmail.com
--- Comment #1 from T
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
Mateusz Piotrowski <0...@freebsd.org> changed:
What|Removed |Added
Keywords||needs-qa
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=229689
Bug ID: 229689
Summary: freebsd-update shouldn't add system breaking comments
to config files
Product: Base System
Version: 11.2-RELEASE
Hardware: Any
16 matches
Mail list logo