public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: David Roundy <droundy@abridgegame.org>, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] darcs mirror of the linux kernel repository
Date: Fri, 12 Nov 2004 13:19:50 +0000	[thread overview]
Message-ID: <tnxis8bqk5l.fsf@arm.com> (raw)
In-Reply-To: <20041111211924.GA1470@elf.ucw.cz> (Pavel Machek's message of "Thu, 11 Nov 2004 22:19:27 +0100")

Pavel Machek <pavel@ucw.cz> writes:
>> In brief, you can get a copy of the latest kernel (converted from the bkcvs
>> branch) using
>
> Would it be possible to get data from www.bkbits.net so that complete
> history is preserved?

I think in the past Larry stated that people should not use the
www.bkbits.net site for retrieving patches (understandable, it
increases the bandwidth usage). But he could use the bk-commits list,
only that I'm not sure all the patches can be cleanly applied in the
order they are posted.

BKCVS has a problem with the timestamps and cvsps cannot be used
properly - in the same changeset, some files can have a timestamp
different by exactly one hour, cvsps generating two patches (with
other patches generated between). For example, the logical change
1.24006 has the modification time for arch/i386/kernel/process.c
22:45:49 but for the rest of the files it is 21:45:49.

Could this get fixed? (I hope it is not intentional :-) )

Catalin


  reply	other threads:[~2004-11-12 13:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-10 12:42 [ANNOUNCE] darcs mirror of the linux kernel repository David Roundy
2004-11-11 21:19 ` Pavel Machek
2004-11-12 13:19   ` Catalin Marinas [this message]
2004-11-12 16:31     ` Pavel Machek
2004-11-12 13:02 ` David Roundy

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=tnxis8bqk5l.fsf@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=droundy@abridgegame.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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