mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@redhat.com>
Cc: Christoph Hellwig <hch@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-rc2-aa1
Date: Mon, 22 Mar 2004 05:16:29 +0100	[thread overview]
Message-ID: <20040322041629.GK3649@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0403212239170.20045-100000@chimarrao.boston.redhat.com>

On Sun, Mar 21, 2004 at 10:43:41PM -0500, Rik van Riel wrote:
> Presuming you'll never debug your code ;)

typedefs are more readable to my eyes, so if they're there it's more
debuggable, infact I liked when Ingo tried to inject the page_t thing
(was him Ingo or somebody else?)

> They're _LINUX_RMAP_H and not _LINUX_OBJRMAP_H.  If you want
> to be consistent you may want to either rename the inclusion
> guards, or the file ;)

I see what you mean now, I agree.

> Only if (1) you're using bitkeeper and (2) you used 'bk mv'
> to move rmap.c to objrmap.c and (3) Linus pulls from your
> bitkeeper tree.

I know this would be expected (this is what happens with arch too in the
explicit mode, the one that I prefer to be strict in the commits), but I
was just trying to say that Miles theory is that BK gets it right
automatically, either that or Linus's scripts gets it right before
injecting it into bk, that is his whole point. Miles sent to Linus
_patches_ (obviously w/o bk, AFIK Miles is not legally allowed to use bk
and Larry even refused him to sell him a commercial licence of bk so
that Miles could use bk while still working on arch) renaming files, and
he then found the renames being catched correctly in the web.

> Unless all 3 of these are true, you're giving bitkeeper more
> credit than it deserves ;)

It may not be bk catching the renames but just an external script that
Linus uses. I don't know.

> > I renamed it primarly because rmap is the common name for the tecnique
> > of traking the pagetables with pte_chains
> 
> Funny, first thing I hear about that ;)

Not sure after all those discussions how you may not have ever noticed
that people uses objrmap to mean something different than rmap, it's
really hard to believe that you never noticed.

  reply	other threads:[~2004-03-22  4:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-21 14:55 2.6.5-rc2-aa1 Andrea Arcangeli
2004-03-21 16:24 ` 2.6.5-rc2-aa1 Christoph Hellwig
2004-03-21 23:43   ` 2.6.5-rc2-aa1 Andrea Arcangeli
2004-03-22  3:43     ` 2.6.5-rc2-aa1 Rik van Riel
2004-03-22  4:16       ` Andrea Arcangeli [this message]
2004-03-22 14:07         ` 2.6.5-rc2-aa1 Rik van Riel
2004-03-22 14:14           ` 2.6.5-rc2-aa1 Andrea Arcangeli
2004-03-22 14:31             ` 2.6.5-rc2-aa1 Hugh Dickins
2004-03-22 14:50               ` 2.6.5-rc2-aa1 Andrea Arcangeli
2004-03-22 15:09                 ` 2.6.5-rc2-aa1 Rik van Riel
2004-03-22 15:21                   ` 2.6.5-rc2-aa1 Andrea Arcangeli
2004-03-22 15:43                 ` 2.6.5-rc2-aa1 Hugh Dickins

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=20040322041629.GK3649@dualathlon.random \
    --to=andrea@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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

all inboxes | Powered by JetHome®