神秘的Github评论是什么意思？ (What do cryptic Github comments mean?)

Are you new to Github and/or contributing to open source projects? Have you seen short messages like LGTM, ACK, NACK, etc. and wondered what they mean?

您是Github的新手和/或致力于开源项目吗？您是否看到过LGTM，ACK，NACK等短消息，并想知道它们是什么意思？

Here you go:

干得好：

LGTM — looks good to me
LGTM-对我来说很好

ACK — acknowledgement, i.e. agreed/accepted change
ACK — 确认，即同意/接受的更改

NACK/NAK —negative acknowledgement, i.e. disagree with change and/or concept
NACK / NAK — 否定确认 ，即不同意更改和/或概念

RFC — request for comments, i.e. I think this is a good idea, lets discuss
RFC-请求评论，即我认为这是一个好主意，让我们讨论

WIP — work in progress, do not merge yet
WIP-进行中，尚未合并

AFAIK/AFAICT — as far as I know / can tell
AFAIK / AFAICT-据我所知/可以告诉

IIRC — if I recall correctly
IIRC —如果我没记错的话

IANAL — “I am not a lawyer”, but I smell licensing issues
IANAL-“我不是律师”， 但我闻到许可问题

Many projects in the crypto space also use the following (popularised by ’s ):

加密领域中的许多项目还使用以下项目(由的流行 )：

Concept ACK — agree with the concept, but haven’t reviewed the changes
概念确认-同意概念，但尚未审查更改

utACK (aka. Untested ACK) — agree with the changes and reviewed them, but didn’t test
utACK(又名未经测试的ACK)—同意更改并进行了检查，但未进行测试

Tested ACK — agree with the changes, reviewed and tested
经测试的ACK-同意更改，经过审查和测试

These answers are usually part of the code review process and you would find them in issues or pull requests in Github.

这些答案通常是代码审查过程的一部分，您会在Github中发现问题或提出请求 。

Honorary mention: +1 as the short form of ACK (and in many cases, Concept ACK). After the , the platform has introduced to declutter comments. No, this is not about making Github your next Facebook :)

荣誉提及： +1是ACK(在许多情况下为Concept ACK)的简称。在，该平台对混乱的评论引入了。不，这不是要让Github成为您的下一个Facebook :)

You would also see the ACKs be included in commit messages, like how the Linux kernel does it since Git is being used:

您还会看到ACK包含在提交消息中，就像Linux内核自使用Git以来所做的那样：

Add get_random_long().Signed-off-by: Daniel Cashman 
    
     Acked-by: Kees Cook 
     
      Cc: "Theodore Ts'o" 
      
       Cc: Arnd Bergmann 
       
        Cc: Greg Kroah-Hartman 
        
         Cc: Catalin Marinas 
         
          Cc: Will Deacon 
          
           Cc: Ralf Baechle 
           
            Cc: Benjamin Herrenschmidt 
            
             Cc: Paul Mackerras 
             
              Cc: Michael Ellerman 
              
               Cc: David S. Miller 
               
                Cc: Thomas Gleixner 
                
                 Cc: Ingo Molnar 
                 
                  Cc: H. Peter Anvin 
                  
                   Cc: Al Viro 
                   
                    Cc: Nick Kralevich 
                    
                     Cc: Jeff Vander Stoep 
                     
                      Cc: Mark Salyzyn 
                      
                       Signed-off-by: Andrew Morton 
                       
                        Signed-off-by: Linus Torvalds

Check out the “” guide for a thorough explanation.

查阅“ ”指南详细说明。

Similar short answers are used widely in software engineering and the open source community as they make communication more efficient.

类似的简短答案可以使沟通更加有效，因此在软件工程和开源社区中得到了广泛使用。

You have surely seen the following in source code — TODO, FIXME, XXX and NOTE — and only wondered what XXX means?

您肯定已经在源代码中看到了以下内容-TODO，FIXME，XXX和NOTE-只是想知道XXX是什么意思？

Interested to see a lot more acronyms with explanation and perhaps a bit of history? Check out . It is the definitive source since 1975.

有兴趣看到更多带有解释的首字母缩写词，也许还有一些历史吗？。自1975年以来，它就是确定的来源。

Bonus trivia: where does ACK/NACK comes from?

奖励琐事 ：ACK / NACK来自哪里？

I would say it came from networking/interface protocols, perhaps the popularity of TCP caused widespread usage.

我想说它来自网络/接口协议，也许TCP的流行引起了广泛的使用。

SYN, SYN/ACK, ACK, FIN, ACK, FIN, ACK.

SYN，SYN / ACK，ACK，FIN，ACK，FIN，ACK。

翻译自:

github是什么意思

转载地址：http://meewd.baihongyu.com/

你可能感兴趣的文章