public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Andrea Arcangeli <andrea@suse.de>
Cc: Larry McVoy <lm@bitmover.com>, Mike Fedyk <mfedyk@matchmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Fwd: Re: Bug Report: 2.4.22-pre5: BUG in page_alloc (fwd)
Date: Mon, 21 Jul 2003 14:31:59 -0700	[thread overview]
Message-ID: <20030721213159.GA7240@work.bitmover.com> (raw)
In-Reply-To: <20030721212155.GF4677@x30.linuxsymposium.org>

On Mon, Jul 21, 2003 at 05:21:55PM -0400, Andrea Arcangeli wrote:
> Hi Larry,
> 
> On Mon, Jul 21, 2003 at 12:45:14PM -0700, Larry McVoy wrote:
> > You don't need the tags, use dates.  You can get the date range you want 
> > with an rlog of the ChangeSet file and then use those dates.
> 
> I realized I could do this, and it can of course be automated with an
> additional bkcvs specific hack in cvsps. But the tag in every file would
> have kept the functionality generic with the already available -r
> option, and since I can't see any downside in the tag in the files, I
> prefer that generic way.

The tags means that each file gets modified for each tag and then we have
to transfer the whole tree after a tag.  It thrashes the hell out of the
disk too, for no good reason.

Also note that there are nowhere near as many tags as there are commits
in the CVS tree.  So by using tags you are restricting yourself to coarse
granularity in your bug hunts.

> But if you're sure the tags aren't coming back we can start adding the
> automation to cvsps.

Please do, we're not adding the tags.  
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-07-21 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030721190226.GA14453@matchmail.com>
2003-07-21 19:45 ` Fwd: Re: Bug Report: 2.4.22-pre5: BUG in page_alloc (fwd) Larry McVoy
2003-07-21 21:21   ` Andrea Arcangeli
2003-07-21 21:31     ` Larry McVoy [this message]
2003-07-21 22:00       ` Andrea Arcangeli
2003-07-21 22:18         ` Larry McVoy
2003-07-29  9:28         ` Andrea Arcangeli
2003-08-17 15:33           ` Andrea Arcangeli

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=20030721213159.GA7240@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=andrea@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.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