From: Catalin Marinas <catalin.marinas@arm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: git@vger.kernel.org
Subject: Re: full kernel history, in patchset format
Date: Mon, 18 Apr 2005 11:07:42 +0100 [thread overview]
Message-ID: <tnx4qe49z4h.fsf@arm.com> (raw)
In-Reply-To: <20050416131528.GB19908@elte.hu> (Ingo Molnar's message of "Sat, 16 Apr 2005 15:15:28 +0200")
Ingo Molnar <mingo@elte.hu> wrote:
> i've converted the Linux kernel CVS tree into 'flat patchset' format,
> which gave a series of 28237 separate patches. (Each patch represents a
> changeset, in the order they were applied. I've used the cvsps
> utility.)
AFAIK, cvsps uses the date/time to create the changesets. There is a
problem with the BKCVS export since some files in the same commit can
have a different time (by an hour). I posted a mail some time ago
about this -
http://marc.theaimsgroup.com/?l=linux-kernel&m=110026570201544&w=2
I read that the old history won't be merged into the new repository
but, if you are interested, I have a script that can do this based on
the "(Logical change ...)" string in the file commit logs and it is
quite fast at generating the patches.
--
Catalin
next prev parent reply other threads:[~2005-04-18 10:03 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-16 13:15 full kernel history, in patchset format Ingo Molnar
2005-04-16 13:35 ` Ingo Molnar
2005-04-16 14:55 ` David Mansfield
2005-04-16 19:18 ` Ingo Molnar
2005-04-16 15:08 ` Francois Romieu
2005-04-16 17:04 ` Linus Torvalds
2005-04-16 17:43 ` Petr Baudis
2005-04-16 15:44 ` Christopher Li
2005-04-16 18:31 ` Junio C Hamano
2005-04-16 18:35 ` Mike Taht
2005-04-16 19:19 ` Junio C Hamano
2005-04-16 16:26 ` Christopher Li
2005-04-16 19:44 ` Junio C Hamano
2005-04-16 19:42 ` Mike Taht
2005-04-16 20:19 ` Daniel Barkalow
2005-04-16 18:46 ` Junio C Hamano
2005-04-16 19:13 ` Jan-Benedict Glaw
2005-04-16 19:23 ` Thomas Gleixner
2005-04-16 18:32 ` Petr Baudis
2005-04-16 18:36 ` Petr Baudis
2005-04-16 19:41 ` Thomas Gleixner
2005-04-16 18:44 ` Linus Torvalds
2005-04-16 19:50 ` Thomas Gleixner
2005-04-16 18:57 ` Petr Baudis
2005-04-16 19:27 ` Junio C Hamano
2005-04-16 19:15 ` Linus Torvalds
2005-04-16 20:35 ` Thomas Gleixner
2005-04-16 23:08 ` David Lang
2005-04-16 19:41 ` Ingo Molnar
2005-04-17 23:31 ` David Woodhouse
2005-04-17 23:39 ` Petr Baudis
2005-04-18 0:06 ` David Woodhouse
2005-04-18 0:35 ` Petr Baudis
2005-04-18 0:45 ` David Woodhouse
2005-04-18 0:50 ` Petr Baudis
2005-04-18 0:51 ` David Woodhouse
2005-04-18 0:59 ` Petr Baudis
2005-04-18 1:16 ` Linus Torvalds
2005-04-18 1:36 ` David Woodhouse
2005-04-18 10:07 ` Catalin Marinas [this message]
2005-04-18 22:41 ` David Mansfield
2005-04-19 8:33 ` Catalin Marinas
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=tnx4qe49z4h.fsf@arm.com \
--to=catalin.marinas@arm.com \
--cc=git@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.