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: Catalin Marinas <catalin.marinas@arm.com>,
	CVSps@dm.cobite.com, linux-kernel@vger.kernel.org,
	Andreas Gruenbacher <agruen@suse.de>
Subject: Re: kernel CVS troubles with cvsps
Date: Wed, 26 Jan 2005 17:14:22 -0800	[thread overview]
Message-ID: <20050127011422.GA15999@bitmover.com> (raw)
In-Reply-To: <20050125190958.GC7587@dualathlon.random>

We're a little busy right now, we'll try and get to this.

On Tue, Jan 25, 2005 at 08:09:58PM +0100, Andrea Arcangeli wrote:
> On Tue, Jan 25, 2005 at 05:10:17PM +0000, Catalin Marinas wrote:
> > I noticed this problem some time ago when trying to see whether the
> > darcs repository is consistent with the BK one:
> > 
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=110026570201544&w=2
> > 
> > A solution is to use the "(Logical change ...)" string within each
> > file's commit log instead of the date (I realised that it is simpler
> > to write a shell script to generate the diffs rather than modifying
> > cvsps).
> 
> Thanks for the confirmation. To me this hour difference looks like a bug
> in bkcvs. It would be nice to get it fixed so we don't have to
> workaround it in cvsps or hack around more scripts.
> 
> Thanks.

-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com

      reply	other threads:[~2005-01-27  1:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 16:42 kernel CVS troubles with cvsps Andrea Arcangeli
2005-01-25 16:58 ` Daniel Jacobowitz
2005-01-25 17:08   ` Andrea Arcangeli
2005-01-25 17:10 ` Catalin Marinas
2005-01-25 19:09   ` Andrea Arcangeli
2005-01-27  1:14     ` Larry McVoy [this message]

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=20050127011422.GA15999@bitmover.com \
    --to=lm@bitmover.com \
    --cc=CVSps@dm.cobite.com \
    --cc=agruen@suse.de \
    --cc=andrea@suse.de \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@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