All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 3.2-rc1
Date: Tue, 8 Nov 2011 03:12:43 +0000	[thread overview]
Message-ID: <20111108031242.GU2203@ZenIV.linux.org.uk> (raw)
In-Reply-To: <CA+55aFzytqbGcOzWvYAo-EnJCeK5mFqdCF5OjMTeM5UBfeyCXw@mail.gmail.com>

On Mon, Nov 07, 2011 at 06:10:02PM -0800, Linus Torvalds wrote:

> Which brings me to a question I already asked on G+ - do people really
> need the old-fashioned patches? The -rc1 patch is about 22MB gzip-9'd,
> and part of the reason is that all those renames cause big
> delete/create diffs. We *could* use git rename patches, but then you'd
> have to apply them with "git apply" rather than the legacy "patch"
> executables. But as it is, the patch is almost a third of the size of
> the tar-ball, which makes me wonder if there's even any point to such
> a big patch?

FWIW, agruen seems to be doing patch(1) development these days; the last
snapshot has this in NEWS:

* Support for most features of the "diff --git" format: renames and copies,
  permission changes, symlink diffs.  Caveats:
  + Binary diffs are not supported yet; patch will complain and skip them.
  + In the "diff --git" format, all the patches are relative to the original
    state of the files to patch, allowing things like criss-cross renames.
    GNU patch will currently fail for such patches.
* Support for double-quoted filenames in the "diff --git" format: when a
  filename in a context diff starts with a double quote, it is interpreted
  as a C string literal.  The escape sequences \\, \", \a, \b, \f, \n, \r,
  \t, \v, and \ooo (a three-digit octal number between 0 and 255) are
  recognized.

Hell knows how long until they release it and distros pick the result, of
course.  Their git tree on git://git.savannah.gnu.org/patch.git is fairly
quiet; there had been a bunch of local fixes since the last snapshot (this
April) but not much else...

  reply	other threads:[~2011-11-08  3:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  2:10 Linux 3.2-rc1 Linus Torvalds
2011-11-08  3:12 ` Al Viro [this message]
2011-11-08  4:26   ` Linus Torvalds
2011-11-08 10:52     ` Geert Uytterhoeven
2011-11-08  6:50 ` Nicholas A. Bellinger
2011-11-08 13:43 ` Udo Steinberg
2011-11-08 14:47   ` Ming Lei
2011-11-08 22:10     ` Rafael J. Wysocki
2011-11-08 14:53 ` Alessandro Suardi
2011-11-08 20:13   ` Linus Torvalds
2011-11-08 20:15     ` Matthew Garrett
2011-11-08 20:44     ` Linus Torvalds
2011-11-08 14:55 ` Nick Bowler
2011-11-08 20:23   ` Linus Torvalds
2011-11-09  7:40     ` Takashi Iwai
2011-11-09  7:40       ` Takashi Iwai
2011-11-09 12:03       ` Wu Fengguang
2011-11-10 11:57       ` Wu Fengguang
2011-11-10 11:57         ` Wu Fengguang
2011-11-08 19:06 ` Thomas Bächler
2011-11-08 23:00 ` Steven Rostedt
2011-11-08 23:53   ` Linus Torvalds
2011-11-09  8:09   ` Borislav Petkov
2011-11-09 13:11   ` Valdis.Kletnieks
2011-11-09 14:20 ` Paul Rolland
2011-11-09 23:23   ` Linus Torvalds
2011-11-09 17:18 ` Randy Dunlap
2011-11-09 17:28   ` Josh Boyer
2011-11-22  1:41     ` Boaz Harrosh
2011-11-22 16:10       ` Josh Boyer
2011-11-22 18:05       ` Alan Cox
2011-11-22 18:29         ` Boaz Harrosh

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=20111108031242.GU2203@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.