Skip to content

Conversation

drawdrop
Copy link
Contributor

No description provided.

Copy link
Contributor

@BrendanGlancy BrendanGlancy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@@ -14,7 +14,7 @@ pub mod udp_payload {
/// +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/// | Length | Checksum |
/// +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
/// We append the data, based on the port the the header
/// We append the data, based on the port the header
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although I agree with the change, does this sentence make sense?

"…based on the port the header"

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, should this be "the port in the header"?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"We append the data, based on the port"

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As in that should be the complete sentence?

I think that makes it a bit ambiguous: it's below a diagram with both "Source Port" and "Destination Port"—to which one is it referring? Or neither?

I think it'd be useful to clarify that as part of this, if possible…?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ahh then it should be "We append the data, based on the destination port"

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perfect—@drawdrop, would you be okay making that minor change?

Otherwise, LGTM.

Copy link
Collaborator

@PsypherPunk PsypherPunk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merging, even with the outstanding comment; will raise a PR to fix that as it's technically separate to the changes herein.

Copy link
Collaborator

@PsypherPunk PsypherPunk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Scratch that: I didn't see the merge conflict.

@drawdrop, if you can fix the merge conflict, this should be good to merge.

@bee-san
Copy link
Owner

bee-san commented Nov 12, 2024

Fixed conflits myself :)

@bee-san bee-san merged commit 4e3c2a5 into bee-san:master Nov 12, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants