On Wed, Jul 1, 2015 at 11:08 AM, Dave Borowitz <dborowitz@xxxxxxxxxx> wrote:
> Signed-off-by: Dave Borowitz <dborowitz@xxxxxxxxxx>
> ---
> Documentation/technical/pack-protocol.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/technical/pack-protocol.txt b/Documentation/technical/pack-protocol.txt
> index 66d2d95..1386840 100644
> --- a/Documentation/technical/pack-protocol.txt
> +++ b/Documentation/technical/pack-protocol.txt
> @@ -481,7 +481,7 @@ references.
> shallow = PKT-LINE("shallow" SP obj-id LF)
>
> command-list = PKT-LINE(command NUL capability-list LF)
We may also want to mark it in this line above as well as in the shallow line?
I think the problem with this part of the documentation is its ambiguity on
what exactly we want to document. The sender SHOULD put an LF, while
the receiver MUST NOT assume the LF is there always, so I guess it's best
to mark it optional from a receivers point of view.
> - *PKT-LINE(command LF)
> + *PKT-LINE(command LF?)
> flush-pkt
>
> command = create / delete / update
> --
> 2.4.3.573.g4eafbef
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html