Page MenuHomeFreeBSD
Differential D8782

update MAINTAINER email to lifanov@FreeBSD.org
ClosedPublic
Actions

Authored by lifanov on Dec 13 2016, 8:38 PM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Mar 21, 11:44 AM
Unknown Object (File)
Tue, Mar 11, 1:32 PM
Unknown Object (File)
Mon, Feb 24, 5:55 AM
Unknown Object (File)
Feb 23 2025, 2:03 PM
Unknown Object (File)
Feb 22 2025, 8:13 PM
Unknown Object (File)
Feb 22 2025, 9:19 AM
Unknown Object (File)
Feb 21 2025, 11:36 PM
Unknown Object (File)
Feb 8 2025, 7:57 PM
View All 89 Files
Subscribers
koobs
mat

Details

Reviewers
matthew
Commits
rP428544: update MAINTAINER to my FreeBSD.org email
Summary

set MAINTAINER to my FreeBSD.org email address for ports that I maintain

Diff Detail

Repository
rP FreeBSD ports repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

lifanov updated this revision to Diff 22894.Dec 13 2016, 8:38 PM
lifanov retitled this revision from to update MAINTAINER email to lifanov@FreeBSD.org.
lifanov updated this object.
lifanov edited the test plan for this revision. (Show Details)
lifanov added a reviewer: matthew.
lifanov added a subscriber: koobs.
Herald added a subscriber: mat. · View Herald TranscriptDec 13 2016, 8:38 PM
matthew accepted this revision.Dec 13 2016, 10:19 PM
matthew edited edge metadata.

LGTM

This revision is now accepted and ready to land.Dec 13 2016, 10:19 PM
Closed by commit rP428544: update MAINTAINER to my FreeBSD.org email (authored by lifanov). · Explain WhyDec 14 2016, 3:47 AM
This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

PathSize
head/
archivers/
innoextract/
2 lines
emulators/
winetricks/
2 lines
games/
alex4/
2 lines
cowsay/
2 lines
endgame-singularity-music/
2 lines
endgame-singularity/
2 lines
gemrb/
2 lines
stonesoup/
2 lines
tome4/
2 lines
wtf/
2 lines
news/
diablo/
2 lines
security/
hashcat-legacy/
2 lines
hashcat/
2 lines
sysutils/
ansible/
2 lines
debootstrap/
2 lines

Diff 22901

View Options

head/archivers/innoextract/Makefile

Show All 22 Lines
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE. .\" SUCH DAMAGE.
.\" .\"
.\" @(#)sigvec.2 8.2 (Berkeley) 4/19/94 .\" @(#)sigvec.2 8.2 (Berkeley) 4/19/94
.\" $FreeBSD$ .\" $FreeBSD$
.\" .\"
.Dd April 19, 1994 .Dd April 2, 2022
.Dt SIGVEC 2 .Dt SIGVEC 2
.Os .Os
.Sh NAME .Sh NAME
.Nm sigvec .Nm sigvec
.Nd software signal facilities .Nd software signal facilities
.Sh LIBRARY .Sh LIBRARY
.Lb libc .Lb libc
.Sh SYNOPSIS .Sh SYNOPSIS
▲ Show 20 Lines • Show All 293 Lines • ▼ Show 20 Lines
.Xr sigprocmask 2 , .Xr sigprocmask 2 ,
.Xr sigsetmask 2 , .Xr sigsetmask 2 ,
.Xr sigsuspend 2 , .Xr sigsuspend 2 ,
.Xr setjmp 3 , .Xr setjmp 3 ,
.Xr siginterrupt 3 , .Xr siginterrupt 3 ,
.Xr signal 3 , .Xr signal 3 ,
.Xr sigsetops 3 , .Xr sigsetops 3 ,
.Xr tty 4 .Xr tty 4
.Sh HISTORY
A
.Fn sigvec
system call first appeared in
.Bx 4.2 .
It was reimplemented as a wrapper around
.Xr sigaction 2
pauamma_gundo.comUnsubmitted
Not Done
Inline Actions

Given it's a wrapper now, shouldn't it be in section 3, like alarm(3) is?

pauamma_gundo.com: Given it's a wrapper now, shouldn't it be in section 3, like alarm(3) is?
in
.Bx 4.3 Reno .
.Sh BUGS .Sh BUGS
This manual page is still confusing. This manual page is still confusing.
View Options

head/emulators/winetricks/Makefile

Show All 22 Lines
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE. .\" SUCH DAMAGE.
.\" .\"
.\" @(#)sigvec.2 8.2 (Berkeley) 4/19/94 .\" @(#)sigvec.2 8.2 (Berkeley) 4/19/94
.\" $FreeBSD$ .\" $FreeBSD$
.\" .\"
.Dd April 19, 1994 .Dd April 2, 2022
.Dt SIGVEC 2 .Dt SIGVEC 2
.Os .Os
.Sh NAME .Sh NAME
.Nm sigvec .Nm sigvec
.Nd software signal facilities .Nd software signal facilities
.Sh LIBRARY .Sh LIBRARY
.Lb libc .Lb libc
.Sh SYNOPSIS .Sh SYNOPSIS
▲ Show 20 Lines • Show All 293 Lines • ▼ Show 20 Lines
.Xr sigprocmask 2 , .Xr sigprocmask 2 ,
.Xr sigsetmask 2 , .Xr sigsetmask 2 ,
.Xr sigsuspend 2 , .Xr sigsuspend 2 ,
.Xr setjmp 3 , .Xr setjmp 3 ,
.Xr siginterrupt 3 , .Xr siginterrupt 3 ,
.Xr signal 3 , .Xr signal 3 ,
.Xr sigsetops 3 , .Xr sigsetops 3 ,
.Xr tty 4 .Xr tty 4
.Sh HISTORY
A
.Fn sigvec
system call first appeared in
.Bx 4.2 .
It was reimplemented as a wrapper around
.Xr sigaction 2
pauamma_gundo.comUnsubmitted
Not Done
Inline Actions

Given it's a wrapper now, shouldn't it be in section 3, like alarm(3) is?

pauamma_gundo.com: Given it's a wrapper now, shouldn't it be in section 3, like alarm(3) is?
in
.Bx 4.3 Reno .
.Sh BUGS .Sh BUGS
This manual page is still confusing. This manual page is still confusing.
View Options

head/games/alex4/Makefile

Show All 22 Lines
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE. .\" SUCH DAMAGE.
.\" .\"
.\" @(#)sigvec.2 8.2 (Berkeley) 4/19/94 .\" @(#)sigvec.2 8.2 (Berkeley) 4/19/94
.\" $FreeBSD$ .\" $FreeBSD$
.\" .\"
.Dd April 19, 1994 .Dd April 2, 2022
.Dt SIGVEC 2 .Dt SIGVEC 2
.Os .Os
.Sh NAME .Sh NAME
.Nm sigvec .Nm sigvec
.Nd software signal facilities .Nd software signal facilities
.Sh LIBRARY .Sh LIBRARY
.Lb libc .Lb libc
.Sh SYNOPSIS .Sh SYNOPSIS
▲ Show 20 Lines • Show All 293 Lines • ▼ Show 20 Lines
.Xr sigprocmask 2 , .Xr sigprocmask 2 ,
.Xr sigsetmask 2 , .Xr sigsetmask 2 ,
.Xr sigsuspend 2 , .Xr sigsuspend 2 ,
.Xr setjmp 3 , .Xr setjmp 3 ,
.Xr siginterrupt 3 , .Xr siginterrupt 3 ,
.Xr signal 3 , .Xr signal 3 ,
.Xr sigsetops 3 , .Xr sigsetops 3 ,
.Xr tty 4 .Xr tty 4
.Sh HISTORY
A
.Fn sigvec
system call first appeared in
.Bx 4.2 .
It was reimplemented as a wrapper around
.Xr sigaction 2
pauamma_gundo.comUnsubmitted
Not Done
Inline Actions

Given it's a wrapper now, shouldn't it be in section 3, like alarm(3) is?

pauamma_gundo.com: Given it's a wrapper now, shouldn't it be in section 3, like alarm(3) is?
in
.Bx 4.3 Reno .
.Sh BUGS .Sh BUGS
This manual page is still confusing. This manual page is still confusing.
View Options

head/games/cowsay/Makefile

Show All 22 Lines
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE. .\" SUCH DAMAGE.
.\" .\"
.\" @(#)sigvec.2 8.2 (Berkeley) 4/19/94 .\" @(#)sigvec.2 8.2 (Berkeley) 4/19/94
.\" $FreeBSD$ .\" $FreeBSD$
.\" .\"
.Dd April 19, 1994 .Dd April 2, 2022
.Dt SIGVEC 2 .Dt SIGVEC 2
.Os .Os
.Sh NAME .Sh NAME
.Nm sigvec .Nm sigvec
.Nd software signal facilities .Nd software signal facilities
.Sh LIBRARY .Sh LIBRARY
.Lb libc .Lb libc
.Sh SYNOPSIS .Sh SYNOPSIS
▲ Show 20 Lines • Show All 293 Lines • ▼ Show 20 Lines
.Xr sigprocmask 2 , .Xr sigprocmask 2 ,
.Xr sigsetmask 2 , .Xr sigsetmask 2 ,
.Xr sigsuspend 2 , .Xr sigsuspend 2 ,
.Xr setjmp 3 , .Xr setjmp 3 ,
.Xr siginterrupt 3 , .Xr siginterrupt 3 ,
.Xr signal 3 , .Xr signal 3 ,
.Xr sigsetops 3 , .Xr sigsetops 3 ,
.Xr tty 4 .Xr tty 4
.Sh HISTORY
A
.Fn sigvec
system call first appeared in
.Bx 4.2 .
It was reimplemented as a wrapper around
.Xr sigaction 2
pauamma_gundo.comUnsubmitted
Not Done
Inline Actions

Given it's a wrapper now, shouldn't it be in section 3, like alarm(3) is?

pauamma_gundo.com: Given it's a wrapper now, shouldn't it be in section 3, like alarm(3) is?
in
.Bx 4.3 Reno .
.Sh BUGS .Sh BUGS
This manual page is still confusing. This manual page is still confusing.
View Options

head/games/endgame-singularity-music/Makefile

Loading...
View Options

head/games/endgame-singularity/Makefile

Loading...
View Options

head/games/gemrb/Makefile

Loading...
View Options

head/games/stonesoup/Makefile

Loading...
View Options

head/games/tome4/Makefile

Loading...
View Options

head/games/wtf/Makefile

Loading...
View Options

head/news/diablo/Makefile

Loading...
View Options

head/security/hashcat-legacy/Makefile

Loading...
View Options

head/security/hashcat/Makefile

Loading...
View Options

head/sysutils/ansible/Makefile

Loading...
View Options

head/sysutils/debootstrap/Makefile

Loading...