git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: [Junio C Hamano] Re: Consolidate SHA1 object file close
Date: Sat, 14 Jun 2008 15:42:33 -0700	[thread overview]
Message-ID: <7viqwbfxk6.fsf@gitster.siamese.dyndns.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 75 bytes --]

Somehow the thread went off-list, so I'm diverting it back to the list...


[-- Attachment #2: Type: message/rfc822, Size: 4037 bytes --]

From: Junio C Hamano <gitster@pobox.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pierre Habouzit <madcoder@debian.org>
Subject: Re: Consolidate SHA1 object file close
Date: Sat, 14 Jun 2008 15:28:27 -0700
Message-ID: <7vmylnfy7o.fsf@gitster.siamese.dyndns.org>

Linus Torvalds <torvalds@linux-foundation.org> writes:

> On Sat, 14 Jun 2008, Junio C Hamano wrote:
>> 
>> I've queued this...
>> 
>> commit 6483925999cde47e5108414ac3f57760394ee2d2
>> Author: Junio C Hamano <gitster@pobox.com>
>> Date:   Fri Jun 13 23:00:51 2008 -0700
>> 
>>     sha1_file.c: dead code removal
>
> Ok, the following three emails will contain three patches on top of that 
> commit that I think are ready for inclusion. They haven't seen a ton of 
> testing, and they are obviously to very core functionality, so in that 
> sense they are a big "scary".

Other than that I had to stop for a few seconds to think at the magic "20
bytes longer", they look scary-but-correct ;-).

I've tagged 1.5.6-rc3 with this (and other fixups), but it appears the
network between me and k.org is crappy today so I'll stop hacking for the
rest of the afternoon and spend time on something else.  Will push the
results out sometime tonight.

Thanks.


             reply	other threads:[~2008-06-14 22:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14 22:42 Junio C Hamano [this message]
2008-06-15 18:08 ` [Junio C Hamano] Re: Consolidate SHA1 object file close Linus Torvalds
2008-06-16  1:13   ` Nicolas Pitre
2008-06-17  5:01   ` Junio C Hamano
2008-06-17 16:30     ` Linus Torvalds
2008-07-04 17:44 ` Pierre Habouzit

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=7viqwbfxk6.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.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).