All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <tr@thomasrast.ch>
To: Johannes Sixt <j6t@kdbg.org>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
	"Jeff King" <peff@peff.net>,
	"Ramsay Jones" <ramsay@ramsay1.demon.co.uk>,
	"Vicent Marti" <tanoku@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>,
	"GIT Mailing-list" <git@vger.kernel.org>
Subject: Re: [PATCH 0/5] fix up 'jk/pack-bitmap' branch
Date: Sat, 09 Nov 2013 22:03:56 +0100	[thread overview]
Message-ID: <87txflnv7n.fsf@linux-k42r.v.cablecom.net> (raw)
In-Reply-To: <527E7021.8060204@kdbg.org> (Johannes Sixt's message of "Sat, 09 Nov 2013 18:25:53 +0100")

Johannes Sixt <j6t@kdbg.org> writes:

> Am 09.11.2013 12:35, schrieb Torsten Bögershausen:
>>
>> If I do like this in compat/bswap.h
>> 
>> # define ntohll(n) (n)
>> # define htonll(n) (n)
>> (on an Intel processor, little endian)
>> 
>> then t5310 passes, even if the uint64_t words are written
>> in little endian to disc instead of big endian.
>
> Of course. You write little endian and also read back little endian;
> that should work just fine, no?
>
> OTOH, if you write with Intel and read with PPC, then you should observe
> misbehavior with the above patch.

Maybe you could check in a simple test that the bitmap for a very
predictable pack (e.g. only one commit) has a certain content, by
checking its hash.  That would guard against accidental format changes.

-- 
Thomas Rast
tr@thomasrast.ch

  reply	other threads:[~2013-11-09 21:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 21:58 [PATCH 0/5] fix up 'jk/pack-bitmap' branch Ramsay Jones
2013-11-07 22:19 ` Jeff King
2013-11-08  1:39   ` Vicent Martí
2013-11-08 17:10   ` Torsten Bögershausen
2013-11-08 18:23     ` Ramsay Jones
2013-11-08 22:29     ` Jeff King
2013-11-09 11:35       ` Torsten Bögershausen
2013-11-09 17:25         ` Johannes Sixt
2013-11-09 21:03           ` Thomas Rast [this message]
2013-11-09 21:21             ` Jeff King

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=87txflnv7n.fsf@linux-k42r.v.cablecom.net \
    --to=tr@thomasrast.ch \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=peff@peff.net \
    --cc=ramsay@ramsay1.demon.co.uk \
    --cc=tanoku@gmail.com \
    --cc=tboegi@web.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.