From: Catalin Marinas <catalin.marinas@arm•com>
To: David Mansfield <david@cobite•com>
Cc: Ingo Molnar <mingo@elte•hu>, git@vger•kernel.org
Subject: Re: full kernel history, in patchset format
Date: Tue, 19 Apr 2005 09:33:21 +0100 [thread overview]
Message-ID: <tnxfyxngo8e.fsf@arm.com> (raw)
In-Reply-To: <426437A2.7080903@cobite.com> (David Mansfield's message of "Mon, 18 Apr 2005 18:41:38 -0400")
David Mansfield <david@cobite•com> wrote:
> Catalin Marinas wrote:
>> 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.
>>
>
> Hmmm. I read that message just now. Is it a matter of 'perfection'
> that is the issue here, or actual correctness when applying the
> patches in order?
I see it as a matter of correctness since in a given BKCVS changeset
(i.e. revision in the ChangeSet,v file) you may miss files. You would
eventually get them, with the same log, but in a different patch. If
you don't care about this, you can call it 'perfection'.
At that time I thought about modifying cvsps to use the "(Logical
change ...)" string instead of time/date for grouping the files but I
realised it is easier with a shell script.
> (perhaps this has now been fixed).
There was no reply to this e-mail. It might have been fixed in the
meantime but I don't think the history was fixed as well.
--
Catalin
prev parent reply other threads:[~2005-04-19 8:29 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
2005-04-18 22:41 ` David Mansfield
2005-04-19 8:33 ` Catalin Marinas [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=tnxfyxngo8e.fsf@arm.com \
--to=catalin.marinas@arm$(echo .)com \
--cc=david@cobite$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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