Received: by 10.236.123.11 with SMTP id u11mr519288yhh.3.1323294778310;
        Wed, 07 Dec 2011 13:52:58 -0800 (PST)
X-BeenThere: django-developers@googlegroups.com
Received: by 10.101.195.10 with SMTP id x10ls2847912anp.1.gmail; Wed, 07 Dec
 2011 13:52:47 -0800 (PST)
Received: by 10.100.246.2 with SMTP id t2mr85885anh.23.1323294767575;
        Wed, 07 Dec 2011 13:52:47 -0800 (PST)
Received: by 10.100.246.2 with SMTP id t2mr85884anh.23.1323294767558;
        Wed, 07 Dec 2011 13:52:47 -0800 (PST)
Return-Path: <c...@oddbird.net>
Received: from lettuce.threepines.org (lettuce.threepines.org. [173.255.192.112])
        by gmr-mx.google.com with ESMTPS id u11si1357168anh.3.2011.12.07.13.52.47
        (version=TLSv1/SSLv3 cipher=OTHER);
        Wed, 07 Dec 2011 13:52:47 -0800 (PST)
Received-SPF: pass (google.com: domain of c...@oddbird.net designates 173.255.192.112 as permitted sender) client-ip=173.255.192.112;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of c...@oddbird.net designates 173.255.192.112 as permitted sender) smtp.mail=c...@oddbird.net
Received: from [209.159.243.83] (helo=[192.168.1.6])
	by lettuce.threepines.org with esmtpsa (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71)
	(envelope-from <c...@oddbird.net>)
	id 1RYPPy-0002SU-K8
	for django-developers@googlegroups.com; Wed, 07 Dec 2011 21:52:46 +0000
Message-ID: <4EDFE0A2.5000903@oddbird.net>
Date: Wed, 07 Dec 2011 14:54:42 -0700
From: Carl Meyer <c...@oddbird.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: django-developers@googlegroups.com
Subject: Re: PUT and post data
References: <7e0a0698-f724-47e3-b39e-1c336b3eb05c@g7g2000vbd.googlegroups.com> <4ED7E65D.8080007@oddbird.net> <bbd6ed3f-3531-4807-b5a6-8ac01b78deab@cs7g2000vbb.googlegroups.com> <19232315.78.1323249933899.JavaMail.geo-discussion-forums@vbjs5> <21b80163-b589-48cf-a90c-5d72d6b80f8f@u6g2000vbg.googlegroups.com> <23518499.85.1323259593914.JavaMail.geo-discussion-forums@vbnd7> <4b97bb02-81ae-4f9e-aef1-9af5e160e...@z1g2000vbx.googlegroups.com>
In-Reply-To: <4b97bb02-81ae-4f9e-aef1-9af5e160e...@z1g2000vbx.googlegroups.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Spam-Status: No (score -1.0): ALL_TRUSTED=-1
X-Spam-Bar: -

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 12/07/2011 07:25 AM, Thibault Jouannic wrote:
> https://github.com/django/django/pull/87
> 
> Hope I did everything right.
> 
> I've read the submitting patches doc, but is a git pull request
> accepted? Otherwise, Should I upload a patch in the closed ticket, or
> open a new one?

Oh, just noticed this question. Generally it's best to err on the side
of opening a new ticket when a previous one has been closed, unless it's
exactly the same issue and the closing was simply in error. In this
case, it's not the same thing, as we're adding documentation of the
current behavior, not adding request.PUT as the previous ticket requested.

Thanks for the documentation patch!

Carl
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk7f4KIACgkQ8W4rlRKtE2f6TACgqQGglLk4rpiMF+lkhnfQwKLs
dMYAnjuGZG8i/aLVltQxlcCtoJU+/Cu1
=QStu
-----END PGP SIGNATURE-----