From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D49A2C432C0 for ; Sun, 1 Dec 2019 14:28:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9D20E2082E for ; Sun, 1 Dec 2019 14:28:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1575210527; bh=23kRnY9l6hVzpnOefG+pIrRM6Q4rbbUBC993dsfYmbQ=; h=References:In-Reply-To:From:Date:Subject:To:Cc:List-ID:From; b=O1X77zYJd8gTMEPYTPisc1fU5o8Xluphy16fIjfR8XYaPBSjbksGWGsoQ8xiK1b+x LJUhmdufnB4sHTFJfCyf2XZqsU+Fvj1T4Z6JLBSOomhYXbKgCdCzDYjjzRKfytRMNO RQFT+bWP6eQLpEiM8MJZ1wsDSDrVOupkvGEE0IFY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726659AbfLAO21 (ORCPT ); Sun, 1 Dec 2019 09:28:27 -0500 Received: from mail-lj1-f194.google.com ([209.85.208.194]:40822 "EHLO mail-lj1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726439AbfLAO20 (ORCPT ); Sun, 1 Dec 2019 09:28:26 -0500 Received: by mail-lj1-f194.google.com with SMTP id s22so17904012ljs.7 for ; Sun, 01 Dec 2019 06:28:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux-foundation.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=l+vQUnn8WZrN5mb0l4AFAbcnrvnGqD368BEzSK9vrjc=; b=baMDvJB6x8ri1qgpZoRR0QipjSxPz0EEG55lu0LWWNDGxqXr35SvhtHnTdr0mqJtTZ 3XZYFpoAzcmAwtQ7IU63gh+QOVuRVOxxwtk+Bpp7Vxliv+9zRWXvpPLzbOFBknSXNohb RpAk8a5uQkYnRxanRCUziu0yMVd0+EBWtyUL8= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=l+vQUnn8WZrN5mb0l4AFAbcnrvnGqD368BEzSK9vrjc=; b=AZxanjSeShxiofhl8qUxAblPmUfdbUG3Q3rZ4NPrMcXhJnlfpWKHARl0MXBz9Oygfu vRfZIn7I9pUZvhY5vIJ4p5haJyC3/P2krjPf7bkEMHvflTle6fILncgh7D+//6Uc6nVo Z2vdKCVeqys21iJS6cxSyxFBbZ6N5XjUqcxC+LQ34LjkO0RsbQ4vKNntRRSCqHPVsrAA CTI8kW2JZvH34G28IkbRv2bTWDfnA52lp6uXDrgE3dhGndFYsrt+btP8Yjq3hO0LnPEj Pt+R4cXGJ7hKvJWmx8XbkwCJES7990PP4IS98WnR1uTchI5pfnj/FZBYwM+Y7bjjeMT8 ZJ9g== X-Gm-Message-State: APjAAAUdgFrtY7c7NXH0/eIJi4dCtxi+XNgr1MsNHsUB/NB+nGuhahjJ Ae0YFawGWkVLtrSvxLKQCEwEY1ge1kA= X-Google-Smtp-Source: APXvYqxhP1grOga0XXWCiNqZEOP8hekeF+zptmzxNMk8OVoa3BB5FOy79MSxuBz/2ayRHMpFRN459Q== X-Received: by 2002:a2e:5751:: with SMTP id r17mr12723432ljd.254.1575210504502; Sun, 01 Dec 2019 06:28:24 -0800 (PST) Received: from mail-lj1-f177.google.com (mail-lj1-f177.google.com. [209.85.208.177]) by smtp.gmail.com with ESMTPSA id e8sm3213798ljb.45.2019.12.01.06.28.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 01 Dec 2019 06:28:23 -0800 (PST) Received: by mail-lj1-f177.google.com with SMTP id u17so9553925lja.4 for ; Sun, 01 Dec 2019 06:28:23 -0800 (PST) X-Received: by 2002:a2e:63dd:: with SMTP id s90mr1932908lje.48.1575210502841; Sun, 01 Dec 2019 06:28:22 -0800 (PST) MIME-Version: 1.0 References: <20191130180301.5c39d8a4@lwn.net> <20191130184512.23c6faaa@lwn.net> In-Reply-To: From: Linus Torvalds Date: Sun, 1 Dec 2019 06:28:06 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH] Documentation: networking: device drivers: Remove stray asterisks To: Junio C Hamano Cc: Jonathan Corbet , Git List Mailing , LKML , "open list:DOCUMENTATION" , =?UTF-8?Q?Jonathan_Neusch=C3=A4fer?= Content-Type: text/plain; charset="UTF-8" Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org On Sat, Nov 30, 2019 at 10:35 PM Junio C Hamano wrote: > > OK, so it appears that the tool is working as documented. Well, yes and no. I think it's a mistake that --no-keep-cr (which is the default) only acts on the outer envelope. Now, *originally* the outer envelope was all that existed so it makes sense in a historical context of "CR removal happens when splitting emails in an mbox". And that's the behavior we have. But then git learnt to do MIME decoding and extracting things from base64 etc, and the CR removal wasn't updated to that change. I guess "documented" is arguable in the sense that the git documentation does talk about "git-mailsplit" as an implementation detail, but still.. Linus