mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stelian Pop <stelian@popies.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [RFC] Linux Kernel SVN Howto - part two
Date: Wed, 16 Feb 2005 17:01:04 +0100	[thread overview]
Message-ID: <20050216160104.GD4372@crusoe.alcove-fr> (raw)

Hi,

[ ... Hoping this message will get past the vger filters and will
  not continue the BK flamewar ... ]

[ ... in fact it did not pass the taboo filters, I modified the
  $subject to pass. I feel it would be better if the list admins
  publicly announced when a subject is being tabooed instead of
  silenty doing it. Think at those reading the archives later... ]

I've updated my Subversion kernel howto and did some work on the
import scripts:
	http://www.popies.net/svn-kernel/

There are now two possibilities to convert the bkcvs repository
into a SVN one:
	* either using the original Ben Collins script, which will
	  map one Linus' changeset into a SVN revision (but all the
	  changesets which occured on another branch and got merged
	  by Linus will be packed into one single SVN revision)

	* or using my modified script which analyses the file deltas
	  and tries to recreate the original changesets (based on the
	  assumption that the log messages for every file involved
	  in a changeset is identical). It works pretty well, if a
	  file hasn't been modified several times on a branch.

The repository creation instructions have also changed a bit, 
improving the time necessary to do the conversion (on my AMD 2000+
I can create the full 2.6 repository in 2 hours using the first
script, 5 hours using the second script).

Feedback welcomed.

Stelian.
-- 
Stelian Pop <stelian@popies.net>

                 reply	other threads:[~2005-02-16 15:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050216160104.GD4372@crusoe.alcove-fr \
    --to=stelian@popies.net \
    --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

all inboxes | Powered by JetHome®