From: Michael Ellerman <michael@ellerman.id.au>
To: Junio C Hamano <junkio@cox.net>
Cc: aneesh.kumar@gmail.com, git@vger.kernel.org
Subject: Re: [PATCH 1/2] gitview: Use new-style classes
Date: Mon, 04 Jun 2007 15:54:55 +1000 [thread overview]
Message-ID: <1180936495.14488.3.camel@concordia.ozlabs.ibm.com> (raw)
In-Reply-To: <7vsl9awva8.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]
On Sat, 2007-06-02 at 02:38 -0700, Junio C Hamano wrote:
> Michael Ellerman <michael@ellerman.id.au> writes:
>
> > Signed-off-by: Michael Ellerman <michael@ellerman.id.au>
>
> Aneesh, this one is in your bailiwick.
>
> Michael, it would have been nicer to have a real log message,
> not just the Subject line, in your message. The Subject line
> says what the patch does in what subarea of the git.git tree,
> which is very appropriate, but that can be seen from the diff
> even if you did not say so. The log message (before your
> Signed-off-by line) is where you describe _why_ you would think
> it is a good change. "What" and "how" are usually evident in
> well written code without much explanation, but "why" is often
> more useful when reviewing the patch, and reading and studying
> the history of the code.
>
> I would have written something like:
>
> This changes the Commit class to use new-style class,
> which has been available since Python 2.2 (Dec 2001).
> This is a necessary step in order to use __slots__
> declaration so that we can reduce the memory footprint
> with my next patch.
>
> I have no strong preference on this change myself. "Classes
> that derive from type" are relatively recent invention but I
> would personally feel that Python 2.2 is ancient enough that
> using it would not pose any practical portability issues, but
> what would I know...
Hi Junio,
Why write my own changelog when you do such a good job! ;)
But seriously, sorry about that. It was a case of me hacking on my local
git tree, not thinking anything would come of it, and then when I saw
the memory reduction from using __slots__ I decided to send off what I'd
done. I should have reset and recommitted with a decent changelog.
cheers
--
Michael Ellerman
OzLabs, IBM Australia Development Lab
wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)
We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2007-06-04 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-30 4:47 [PATCH 1/2] gitview: Use new-style classes Michael Ellerman
2007-05-30 4:47 ` [PATCH 2/2] gitview: Define __slots__ for Commit Michael Ellerman
2007-06-02 9:38 ` [PATCH 1/2] gitview: Use new-style classes Junio C Hamano
2007-06-04 5:54 ` Michael Ellerman [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=1180936495.14488.3.camel@concordia.ozlabs.ibm.com \
--to=michael@ellerman.id.au \
--cc=aneesh.kumar@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).