On Fri, 06 May 2016, Tormod Volden wrote: > PS. I didn't think about it initially, but I guess "NACK" means > "thanks for your patch and your interest in the developer reference, > but I don't think this is the best solution."
That's pretty much correct, yes. NACK in this context implies that whatever you proposed was carefully considered by the person "NACK'ing" it, and then rejected. An explanation for the rejection should be provided along with the "NACK". It is very common lingo on Linux-releated FLOSS development mailing lists, when rejecting a changes proposal (patch), etc. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh
