Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
What's new
7
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Open sidebar
Per Cederqvist
lyskom-server-ceder-1616-generations-topgit
Commits
2a5a1961
Commit
2a5a1961
authored
Sep 06, 2000
by
Per Cederqvist
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
(The Misc-Info List): Fix the description of the visibility of bcc-recpt.
parent
15feb328
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
6 additions
and
3 deletions
+6
-3
doc/Protocol-A.texi
doc/Protocol-A.texi
+6
-3
No files found.
doc/Protocol-A.texi
View file @
2a5a1961
...
...
@@ -2,7 +2,7 @@
@c
@c FIXME: Explain how the garb works with nice and keep-commented
@c
@c
$
Id: Protocol
-
A.texi,v
1
.
10
2
2000
/
09
/
06
1
7
:
07
:
03
ceder Exp
$
@c
$
Id: Protocol
-
A.texi,v
1
.
10
3
2000
/
09
/
06
1
9
:
39
:
17
ceder Exp
$
@c
%**start of header
@setfilename protocol-a.info
@settitle LysKOM Protocol A
...
...
@@ -705,8 +705,11 @@ conference status of the involved conference. (That is, as long as the
conference isn't secret everybody is allowed to see the carbon-copy
recipient group.)
A BCC recipient group is only visible to members and supervisors of the
recipient. This is enforced by the server.
A BCC recipient group is basically only visible to members and
supervisors of the recipient. Persons that have the right to become a
member of the recipient can also see it, as can the author of the text
(unless the recipient is secret to him). This is enforced by the
server.
This type of group was introduced in protocol version 10. When
old-style calls such as get-text-stat-old (@pxref
{
get-text-stat-old
}
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment