Nurah.lee

 Rujukan artikel :  Ignoring in Git: How To Use .gitignore Files When  making commits to any Git repository , you’ll choose the files you want to stage and then you’ll commit them. But you might not want to commit every single one of your files—there are files that never need to get committed. This is where the .gitignore file is useful: it tells Git exactly which files to ignore and never track. Let’s take a look. What is gitignore? When you’re working in your copy, Git  watches every file  in and considers it in three ways: Tracked: You’ve already staged or committed the file. Untracked: You’ve not staged or committed. Ignored: You’ve explicitly told Git to ignore the file(s). The .gitignore file tells Git which  files to ignore  when committing your project to the GitHub repository. gitignore is located in the root directory of your repo. The .gitignore file itself is a plain text document. Here’s an  example .gitignore file : Copy # Binaries for programs and plugins *. exe *. exe

Reference : https://osqa-ask.wireshark.org/questions/20423/pshack-wireshark-capture/ This is basic TCP communications flow. The ACK indicates that a host is acknowledging having received some data, and the PSH,ACK indicates the host is acknowledging receipt of some previous data and also transmitting some more data. Google will let you search for more info about basic TCP communication.   ACK means that the machine sending the packet with ACK is acknowledging data that it had received from the other machine. In TCP, once the connection is established,   all   packets sent by either side will contain an ACK, even if it's just re-acknowledging data that it's already acknowledged. PSH is an indication by the sender that, if the receiving machine's TCP implementation has not yet provided the data it's received to the code that's reading the data (program, or library used by a program), it should do so at that point. To quote  RFC 793 , the official specification for TCP