On Thu, Aug 23, 2007 at 10:06:01PM +0200, Erik Forsberg wrote:
> "Martin v. L?wis" <[EMAIL PROTECTED]> writes:
>
> >> When editing my details I saw there is a field for my timezone. The
> >> comment says: "this is a numeric hour offset, the default is UTC", so
> >> I'm assuming it counts in whole
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
>> When editing my details I saw there is a field for my timezone. The
>> comment says: "this is a numeric hour offset, the default is UTC", so
>> I'm assuming it counts in whole hours (fine for me, not s
On 8/23/07, Martin von Löwis <[EMAIL PROTECTED]> wrote:
> We have completed the conversion to Roundup as the bug tracker
> for Python; the new tracker is now life at
>
> http://bugs.python.org/
>
> It has all reports from the SourceForge tracker, along with
> all messages and files that had been
> When editing my details I saw there is a field for my timezone. The
> comment says: "this is a numeric hour offset, the default is UTC", so
> I'm assuming it counts in whole hours (fine for me, not so fine for
> people in e.g. India, unless it accepts decimal notation). I have two
> issues with
On 2007-08-23 18:50, Martin von Löwis wrote:
> We have completed the conversion to Roundup as the bug tracker
> for Python; the new tracker is now life at
>
> http://bugs.python.org/
So far, I have one issue with the new tracker: the timezone.
When editing my details I saw there is a field for
We have completed the conversion to Roundup as the bug tracker
for Python; the new tracker is now life at
http://bugs.python.org/
It has all reports from the SourceForge tracker, along with
all messages and files that had been attached.
To edit bug reports, you still need to log in. We have mi
