Git development
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Pieter de Bie <pdebie@ai.rug.nl>
Cc: Junio C Hamano <gitster@pobox.com>,
	Git Mailinglist <git@vger.kernel.org>
Subject: Re: [PATCH v3] builtin-fast-export: Add importing and exporting of revision marks
Date: Wed, 11 Jun 2008 19:45:27 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.1.00.0806111941160.1783@racer> (raw)
In-Reply-To: <1213183024-60013-1-git-send-email-pdebie@ai.rug.nl>

Hi,

On Wed, 11 Jun 2008, Pieter de Bie wrote:

>   I actually had this new patch ready, but I was hoping Dscho would answer
>   this first:
>   
> On 7 jun 2008, at 18:37, Junio C Hamano wrote:
> >Oh, I was not complaining about the one-fourthness.  I was wondering why
> >"(uint32_t *)", which makes it look like the type itself has very deep
> >meaning for this computation, was used, instead of "(char *)" or something
> >that makes it much clearer that what could be pointed at by the pointer
> >does not matter and you are only using them as fake integers.  If there is
> >such a deep meaning, it needs documented, and if there isn't then probably
> >the use of (uint32_t *) should also be fixed.
>   
>   since I don't know the answer to that :)

I think that your patch does not need to address that, as the logic is (or 
should be) confined to the functions markt_object() and get_object_mark() 
(except that you have to split off mark_to_ptr() from 
mark_object(), as you did).

Unfortunately, I did not yet have time to look up the discussion on the 
mailing list that led me to implement this funny pointer arithmetic.

Ciao,
Dscho

  parent reply	other threads:[~2008-06-11 18:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-04 20:55 [PATCH] builtin-fast-export: Add importing and exporting of revision marks Pieter de Bie
2008-06-05  0:00 ` Johannes Schindelin
2008-06-05 10:46   ` Pieter de Bie
2008-06-05 10:52     ` [PATCH v2] " Pieter de Bie
2008-06-05 13:35       ` Johannes Schindelin
2008-06-06 23:09       ` Junio C Hamano
2008-06-07 13:06         ` Pieter de Bie
2008-06-07 15:19           ` Johannes Schindelin
2008-06-07 16:37             ` Junio C Hamano
2008-06-11 19:45               ` Johannes Schindelin
2008-06-07 13:25       ` [PATCH] Documentation/fast-export: Document --import-marks and --export-marks options Pieter de Bie
2008-06-07 15:20         ` Johannes Schindelin
2008-06-10  6:47         ` Junio C Hamano
2008-06-11 11:17           ` [PATCH v3] builtin-fast-export: Add importing and exporting of revision marks Pieter de Bie
2008-06-11 11:24             ` Pieter de Bie
2008-06-11 18:45             ` Johannes Schindelin [this message]
2008-06-11 21:43             ` Junio C Hamano
2008-06-05 13:31     ` [PATCH] " Johannes Schindelin

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=alpine.DEB.1.00.0806111941160.1783@racer \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=pdebie@ai.rug.nl \
    /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