From: Sverre Rabbelier <srabbelier@gmail.com>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: Jari Aalto <jari.aalto@cante.net>, git@vger.kernel.org
Subject: Re: [PATCH RFC 0/5] Patches to avoid reporting conversion changes.
Date: Sun, 18 Apr 2010 00:07:16 +0200 [thread overview]
Message-ID: <n2kfabb9a1e1004171507r3f51d18bq3ff60831370f9b10@mail.gmail.com> (raw)
In-Reply-To: <86eiidan59.fsf@red.stonehenge.com>
Heya,
On Sat, Apr 17, 2010 at 21:34, Randal L. Schwartz <merlyn@stonehenge.com> wrote:
> Yes, once it's already *in* the program. But I bet you had to *look
> them up* to add them.
Yes, but once they're there nobody has to look them up. It's moving
the problem from having to look up what it means on _and_ write, to
just write.
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2010-04-17 22:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 16:09 [PATCH RFC 0/5] Patches to avoid reporting conversion changes Henrik Grubbström (Grubba)
2010-04-16 16:09 ` [PATCH RFC 1/5] sha1_file: Added index_blob() Henrik Grubbström (Grubba)
2010-04-16 16:09 ` [PATCH RFC 2/5] cache: Added ce_norm_sha1() and related cache_entry fields Henrik Grubbström (Grubba)
2010-04-16 16:10 ` [PATCH RFC 3/5] cache: Added index extension "NORM" Henrik Grubbström (Grubba)
2010-04-16 16:10 ` [PATCH RFC 4/5] reachable: Made the gc aware of the ce_norm_sha1 Henrik Grubbström (Grubba)
2010-04-16 16:10 ` [PATCH RFC 5/5] cache: Use ce_norm_sha1() Henrik Grubbström (Grubba)
2010-04-20 7:25 ` Junio C Hamano
2010-04-20 15:39 ` Henrik Grubbström
2010-04-20 19:12 ` Junio C Hamano
2010-04-25 11:25 ` Henrik Grubbström
2010-04-16 18:02 ` [PATCH RFC 0/5] Patches to avoid reporting conversion changes Jari Aalto
2010-04-16 18:06 ` Randal L. Schwartz
2010-04-17 19:32 ` Jari Aalto
2010-04-17 19:34 ` Randal L. Schwartz
2010-04-17 22:07 ` Sverre Rabbelier [this message]
2010-04-17 22:32 ` Jakub Narebski
2010-04-17 22:47 ` Sverre Rabbelier
2010-04-17 22:58 ` Randal L. Schwartz
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=n2kfabb9a1e1004171507r3f51d18bq3ff60831370f9b10@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=git@vger.kernel.org \
--cc=jari.aalto@cante.net \
--cc=merlyn@stonehenge.com \
/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).