From: Chuck Lever <cel@citi.umich.edu>
To: Catalin Marinas <catalin.marinas@gmail.com>
Cc: Blaisorblade <blaisorblade@yahoo.it>, git@vger.kernel.org
Subject: Re: [PATCH] Stgit - gitmergeonefile.py: handle removal vs. changes
Date: Sat, 07 Jan 2006 20:50:49 -0500 [thread overview]
Message-ID: <43C06FF9.4070908@citi.umich.edu> (raw)
In-Reply-To: <43BFA499.3020202@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 549 bytes --]
Catalin Marinas wrote:
>>Also, another note: I just found Bruce Eckel mentioning pychecker, which is a
>>static code checker for Python (to perform the checks a compiler would
>>normally do). I've not the time to investigate more myself, but I hope it can
>>be useful to you.
>>
>>
>
> Thanks. I'll give it a try.
i already ran pychecker against everything but gitmergeonefile.py... it
found a few things that you have already integrated (like that weird
behavior around using empty lists as the default value for function
arguments). fyi...
[-- Attachment #2: cel.vcf --]
[-- Type: text/x-vcard, Size: 466 bytes --]
begin:vcard
fn:Chuck Lever
n:Lever;Charles
org:Network Appliance, Incorporated;Open Source NFS Client Development
adr:535 West William Street, Suite 3100;;Center for Information Technology Integration;Ann Arbor;MI;48103-4943;USA
email;internet:cel@citi.umich.edu
title:Member of Technical Staff
tel;work:+1 734 763-4415
tel;fax:+1 734 763 4434
tel;home:+1 734 668-1089
x-mozilla-html:FALSE
url:http://troy.citi.umich.edu/u/cel/
version:2.1
end:vcard
prev parent reply other threads:[~2006-01-08 1:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-13 19:42 [PATCH] Stgit - gitmergeonefile.py: handle removal vs. changes Paolo 'Blaisorblade' Giarrusso
2005-11-15 9:54 ` Catalin Marinas
2005-11-16 14:44 ` Blaisorblade
2005-11-17 22:10 ` Catalin Marinas
2005-11-17 22:50 ` Chuck Lever
2005-11-21 21:32 ` Catalin Marinas
2005-12-30 17:59 ` Blaisorblade
2006-01-07 11:23 ` Catalin Marinas
2006-01-08 1:50 ` Chuck Lever [this message]
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=43C06FF9.4070908@citi.umich.edu \
--to=cel@citi.umich.edu \
--cc=blaisorblade@yahoo.it \
--cc=catalin.marinas@gmail.com \
--cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).