Re: [ietf-types] Status of application/patch or text/patch?
Julian Reschke <julian.reschke@gmx.de> Wed, 11 July 2012 07:24 UTC
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D298B21F85D8 for <ietf-types@ietfa.amsl.com>; Wed, 11 Jul 2012 00:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.107
X-Spam-Level:
X-Spam-Status: No, score=-105.107 tagged_above=-999 required=5 tests=[AWL=-2.508, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3HapXGYUOz60 for <ietf-types@ietfa.amsl.com>; Wed, 11 Jul 2012 00:24:32 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 20B0E21F85D5 for <ietf-types@ietf.org>; Wed, 11 Jul 2012 00:24:29 -0700 (PDT)
Received: (qmail invoked by alias); 11 Jul 2012 07:24:58 -0000
Received: from p5DD94F16.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.79.22] by mail.gmx.net (mp071) with SMTP; 11 Jul 2012 09:24:58 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18z2pMOMWYzxpm9DVONyi7Z/Kzl9i5oV3+Ty9ZXlv lVkzLWVBEN5OKj
Message-ID: <4FFD2A49.8030709@gmx.de>
Date: Wed, 11 Jul 2012 09:24:57 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Jon Moore <jonm@jjmoore.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com>
In-Reply-To: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Jul 2012 07:24:34 -0000
On 2012-07-11 03:12, Jon Moore wrote: > Hi folks, > > Given the recent arrival of HTTP PATCH in RFC 5789[1], it seems like 2+ years :-) > registering a media type for the output of the 'diff' utility would be > a good idea. I found this thread from 2007 where Julian Reschke > proposed this exact thing: > > http://www.ietf.org/mail-archive/web/ietf-types/current/msg00591.html > > Does anyone know where this landed? I'd like to pick up the torch and Nowhere, as far as I can tell. > at least work on text/diff (using the unified diff format, and limited > to those diffs that can be rendered as valid text/* types). I've > started putting together an Internet Draft for it, but was wondering > if this had actually run into technical trouble, or if it just ran out > of steam in 2007. > > Any guidance would be appreciated! My recollection is that I got lost in the output format variations and potential copyrights. So please go ahead; the IETF APPSAWG mailing list probably is a good place to get feedback. Best regards, Julian
- [ietf-types] Status of application/patch or text/… Jon Moore
- Re: [ietf-types] Status of application/patch or t… Julian Reschke
- Re: [ietf-types] Status of application/patch or t… Jon Moore
- Re: [ietf-types] Status of application/patch or t… Simon Josefsson
- Re: [ietf-types] Status of application/patch or t… Jon Moore
- Re: [ietf-types] Status of application/patch or t… Simon Josefsson
- Re: [ietf-types] Status of application/patch or t… Steve Allen
- Re: [ietf-types] Status of application/patch or t… Julian Reschke
- Re: [ietf-types] Status of application/patch or t… Simon Josefsson
- Re: [ietf-types] Status of application/patch or t… Julian Reschke
- Re: [ietf-types] Status of application/patch or t… Bjoern Hoehrmann
- Re: [ietf-types] Status of application/patch or t… Julian Reschke
- Re: [ietf-types] Status of application/patch or t… Bjoern Hoehrmann
- Re: [ietf-types] Status of application/patch or t… Eric Prud'hommeaux
- Re: [ietf-types] Status of application/patch or t… Jon Moore
- Re: [ietf-types] Status of application/patch or t… Paul Libbrecht
- Re: [ietf-types] Status of application/patch or t… Eric Prud'hommeaux
- Re: [ietf-types] Status of application/patch or t… Jon Moore
- Re: [ietf-types] Status of application/patch or t… Paul Libbrecht
- Re: [ietf-types] Status of application/patch or t… Martin J. Dürst
- Re: [ietf-types] Status of application/patch or t… Eric Prud'hommeaux