From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH] Add SubmittingPatches
Date: Mon, 15 Aug 2005 17:37:48 -0700 [thread overview]
Message-ID: <7vbr3ysomb.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0508151715520.3553@g5.osdl.org> (Linus Torvalds's message of "Mon, 15 Aug 2005 17:24:56 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> And 4.58 needs at least this
> diff-tree 8326dd8350be64ac7fc805f6563a1d61ad10d32c (from e886a61f76edf5410573e92e38ce22974f9c40f1)
> Author: Linus Torvalds <torvalds@g5.osdl.org>
> Date: Mon Aug 15 17:23:51 2005 -0700
>
> Fix pine whitespace-corruption bug
>
> There's no excuse for unconditionally removing whitespace from
> the pico buffers on close.
Wow.
This is a _terrible_ one. Isn't pico code also supposed to be a
standalone editor of some sort? I wonder how anybody could
tolerate this kind of "dictatorship ;-)".
At least the changelog entry seems to say that 4.60 removed this
"feature".
next prev parent reply other threads:[~2005-08-16 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 9:08 [PATCH] Add SubmittingPatches Junio C Hamano
2005-08-15 23:50 ` Johannes Schindelin
2005-08-16 0:24 ` Linus Torvalds
2005-08-16 0:37 ` Junio C Hamano [this message]
2005-08-16 1:03 ` Johannes Schindelin
2005-08-16 1:23 ` Junio C Hamano
2005-08-16 1:41 ` Johannes Schindelin
2005-08-16 3:28 ` Ryan Anderson
2005-08-16 15:22 ` Submitting patches w/ Thunderbird [was: Re: [PATCH] Add SubmittingPatches] A Large Angry SCM
2005-08-16 0:25 ` [PATCH] Add SubmittingPatches Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vbr3ysomb.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).