Re: [ietf-types] Status of application/patch or text/patch?
Jon Moore <jonm@jjmoore.net> Wed, 11 July 2012 09:02 UTC
Return-Path: <jonm@jjmoore.net>
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 C925A21F8683 for <ietf-types@ietfa.amsl.com>; Wed, 11 Jul 2012 02:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level:
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 0LSvtM+36Nov for <ietf-types@ietfa.amsl.com>; Wed, 11 Jul 2012 02:02:04 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0455321F8680 for <ietf-types@ietf.org>; Wed, 11 Jul 2012 02:02:03 -0700 (PDT)
Received: by qaea16 with SMTP id a16so729549qae.10 for <ietf-types@ietf.org>; Wed, 11 Jul 2012 02:02:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:x-mailer:from:subject:date:to :x-gm-message-state; bh=xF77/b4foGGi2K9kFx9N3vTda1l7CyU95hdyvm7VKGU=; b=dv1wHVSI9WBm5+knIWfyswM+MLWa9u6pe3+VyPd35lIbNakgf/klmYHrG/iZBWwpGx y7/z3C09TvIR8k3uQYzayzuX2NOCaAJvYiXy8T0A24CXIGW5TaXTqbrES2Sg1frDuo4I uhQybz1zmzwmUvM85I0amWRyKYaelZhLi3gAB75vJnkSmYeA/nHXv+wVsBcZjjQU7MY3 lwU3wHpdGK9AquQO/4RNLXLoyrLNeAWzbrOVSzLn2JM+2NUTOBQVj2sw0YicdqokCJCk Xt/RaJFQdFbtO8FuLq2fYkiHVY1kTnMR3oF8Oy9Q7bR8HGEyOkLybyYXedOpxFU/yR/F 9c/g==
Received: by 10.229.136.200 with SMTP id s8mr25387871qct.46.1341997353478; Wed, 11 Jul 2012 02:02:33 -0700 (PDT)
Received: from [192.168.154.100] (c-68-32-29-233.hsd1.pa.comcast.net. [68.32.29.233]) by mx.google.com with ESMTPS id t6sm2492882qal.18.2012.07.11.02.02.30 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 Jul 2012 02:02:31 -0700 (PDT)
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <4FFD2A49.8030709@gmx.de>
In-Reply-To: <4FFD2A49.8030709@gmx.de>
Mime-Version: 1.0 (iPhone Mail 8J2)
Content-Type: text/plain; charset="us-ascii"
Message-Id: <7CB5C4AB-E6CD-4357-9DA0-8A541DE333CA@jjmoore.net>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (8J2)
From: Jon Moore <jonm@jjmoore.net>
Date: Wed, 11 Jul 2012 05:02:26 -0400
To: Julian Reschke <julian.reschke@gmx.de>
X-Gm-Message-State: ALoCoQnvulCJ3bqAmyy/zai7hsK61ea8Ux0WoMN3KTXwgPvqSooPeQUg0XpUJZwzbUuY00+TYhgu
Cc: "ietf-types@ietf.org" <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 09:02:05 -0000
Well, 2+ years is pretty recent in IETF time. :) Thanks for the guidance, I'll follow up with APPSAWG. Jon ........ Jon Moore On Jul 11, 2012, at 3:24 AM, Julian Reschke <julian.reschke@gmx.de> wrote: > 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