git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Jeff King <peff@peff.net>
Subject: [PATCH 0/3] Using a bit more decoration
Date: Mon,  8 Apr 2013 16:01:51 -0700	[thread overview]
Message-ID: <1365462114-8630-1-git-send-email-gitster@pobox.com> (raw)
In-Reply-To: <20130408210903.GC9649@sigill.intra.peff.net>

This comes on top of the two "decorate" patches that introduced the
clear_decoration() function.

I am not sure if pre-parsing and sharing the encoding values in-core
would affect performance very much, but now we have 2 bytes (or 6
bytes, if you are on 64-bit archs) free to use in "struct commit"
for later use (e.g. extra object flags that are relevant only for
commit objects, without having to widen "struct object").

Junio C Hamano (3):
  commit: shrink "indegree" field
  commit: rename parse_commit_date()
  commit: add get_commit_encoding()

 commit.c    | 138 ++++++++++++++++++++++++++++++++++++++++++++++++++----------
 commit.h    |   5 ++-
 pretty.c    |  33 +--------------
 sequencer.c |  23 +---------
 4 files changed, 122 insertions(+), 77 deletions(-)

-- 
1.8.2.1-450-gd047976

  parent reply	other threads:[~2013-04-08 23:02 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-08  6:14 [PATCH 2/2] decorate: add "clear_decoration()" Junio C Hamano
2013-04-08 21:09 ` Jeff King
2013-04-08 21:22   ` Junio C Hamano
2013-04-08 23:01   ` Junio C Hamano [this message]
2013-04-08 23:01     ` [PATCH 1/3] commit: shrink "indegree" field Junio C Hamano
2013-04-09  3:52       ` Jeff King
2013-04-08 23:01     ` [PATCH 2/3] commit: rename parse_commit_date() Junio C Hamano
2013-04-08 23:01     ` [PATCH 3/3] commit: add get_commit_encoding() Junio C Hamano
2013-04-09  3:51     ` [PATCH 0/3] Using a bit more decoration Jeff King
2013-04-09  4:17       ` Junio C Hamano
2013-04-09  4:39         ` Jeff King
2013-04-09  4:54           ` Junio C Hamano
2013-04-09  6:52             ` Jeff King
2013-04-09 20:06               ` Junio C Hamano
2013-04-09  4:37       ` Junio C Hamano

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=1365462114-8630-1-git-send-email-gitster@pobox.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.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).