summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRichard Sharpe <sharpe@samba.org>2005-04-06 16:48:28 +0000
committerGerald (Jerry) Carter <jerry@samba.org>2007-10-10 13:11:28 -0500
commit6d0c1be1a4d52f7214dd7aedfe0ea639402fc18e (patch)
treecaaf340e60ad895d1c2da22b387cc9449c7fd5db
parent7c6c366150022d6a745dcf18ed67bd264bc9c55d (diff)
downloadsamba-6d0c1be1a4d52f7214dd7aedfe0ea639402fc18e.tar.gz
samba-6d0c1be1a4d52f7214dd7aedfe0ea639402fc18e.tar.bz2
samba-6d0c1be1a4d52f7214dd7aedfe0ea639402fc18e.zip
r6226: A couple of small typos ...
(This used to be commit d2c5320a18821439e49d3f7bffebc47129b8b057)
-rw-r--r--prog_guide.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/prog_guide.txt b/prog_guide.txt
index d4a170b278..f5ac600f88 100644
--- a/prog_guide.txt
+++ b/prog_guide.txt
@@ -207,7 +207,7 @@ an idea of what I am talking about.
In Samba3 many of the core wire structures in the SMB protocol were
never explicitly defined in Samba. Instead, our parse and generation
functions just worked directly with wire buffers. The biggest problem
-with this is that is tied our parse code with out "business logic"
+with this is that is tied our parse code with our "business logic"
much too closely, which meant the code got extremely confusing to
read.
@@ -395,7 +395,7 @@ function, so smbd has a _send() function and the parse function for
each SMB.
As an example go and have a look at reply_getatr_send() and
-reply_getatr() in smbd/reply.c. Read them? Good.
+reply_getatr() in smb_server/reply.c. Read them? Good.
Notice that reply_getatr() sets up the req->async structure to contain
the send function. Thats how the backend gets to do an async reply, it