You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Ben Collins <bc...@debian.org> on 2003/06/15 14:09:06 UTC
[bcollins@debian.org: bkSVN live]
----- Forwarded message from Ben Collins <bc...@debian.org> -----
From: Ben Collins <bc...@debian.org>
To: linux-kernel@vger.kernel.org
Cc: Larry McVoy <lm...@bitmover.com>
Subject: bkSVN live
X-Mailing-List: linux-kernel@vger.kernel.org
X-Spam-Status: No, hits=-8.7 required=5.0
tests=BAYES_01,SIGNATURE_LONG_DENSE,USER_AGENT_MUTT,
X_MAILING_LIST
autolearn=ham version=2.55
X-Spam-Level:
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
Thanks to Larry, the bkSVN repo is now live. It's actually bkcvs2svn,
since I am using bkcvs's metadata. However subversion is able to make
better use of the metadata than CVS can. You can get better log output,
for one. Also, you can more easily determine the scope of a change,
since subversion supports changesets.
If you aren't familiar with subversion, please visit the URL in my sig.
Please do not ask me a lot of questions about it. First off, it's very
well documented, and second off, I am not what I would consider an
expert on the internals of SVN.
And please DO NOT email linux-kernel with any comments, suggestions,
questions regarding subversion. It is way off topic. Subversion !=
BitKeeper, and it's not intended to replace it. So this isn't a
competition. Otherwise, Larry wouldn't feel so comfortable with hosting
the repo :)
For those that know SVN, you need a recent (e.g. upcoming 0.24 release
of SVN, or current trunk) client. I am using revision r6227. If you need
a client just for testing, you can get a ra_svn only static binary from
http://www.phunnypharm.org/pub/svn/clients/linux/. i386, sparc and ia64
are there. I can build more if needed (I think I have access to just
about anything). You'll need glibc 2.3 for the static clients since it
uses NSS modules, and well, it just wont work with 2.2/2.1/etc. If you
want to build your own, remember, you don't need berkeley DB, or neon
to access this repo.
Now, finally the SVN URL's:
svn://kernel.bkbits.net/linux-2.4
svn://kernel.bkbits.net/linux-2.5
WAIT. If you don't know anything about SVN repo layouts, just remember
this:
REPO_BASE/trunk Primary (aka HEAD) development
REPO_BASE/tags/* Tagged revsions
REPO_BASE/branches/* Other development lines (not used in bkSVN)
So, to get the main development for say 2.5:
# svn co svn://kernel.bkbits.net/linux-2.5/trunk linux-2.5-bkbits
Will checkout the main 2.5 trunk into a directory called
linux-2.5-bkbits. Then you can cd into that directory and do "svn up"
just like CVS :). The "svn log" output is much better than in CVS, since
you can do things like "svn log drivers/usb" and get a single list of
revisions that affected anything in drivers/usb, unlike CVS where you
would get history for all files seperately. "svn help" is really useful
aswell.
If you want to checkout a particular version:
# svn co svn://kernel.bkbits.net/linux-2.5/tags/v2.5.60 linux-2.5.60
Or diff versions, via URL, without a working copy:
# svn diff svn://kernel.bkbits.net/linux-2.4/tags/v2.4.19 \
svn://kernel.bkbits.net/linux-2.4/tags/v2.4.20 > patch-2.4.20.diff
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
----- End forwarded message -----
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [bcollins@debian.org: bkSVN live]
Posted by Ben Collins <bc...@debian.org>.
On Mon, Jun 16, 2003 at 03:27:59AM -0500, cmpilato@collab.net wrote:
> junkio@cox.net writes:
>
> > My understanding was that renames are shown by "(from /original/path:rev)"
> > in "svn log -v" output, so I was expecting to see something like:
> >
> > D /trunk/drivers/ide/aec62xx.c
> > ...
> > A /trunk/drivers/ide/pci/aec62xx.c (from /trunk/drivers/ide/aec62xx.c:1)
>
> Your understanding is correct. It would appear that renames are
> handled strictly as deletes and adds (without copy history) in the
> mirroring code.
That's mainly because I am getting the info from CVS, which doesn't
support them either.
When I was able to do bk2svn directly, I was supporting renames.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [bcollins@debian.org: bkSVN live]
Posted by Stefan Monnier <mo...@rum.cs.yale.edu>.
> Your understanding is correct. It would appear that renames are
> handled strictly as deletes and adds (without copy history) in the
> mirroring code.
Which is no wonder, since it goes through CVS.
Recovering the move-info is probably possible, but more work,
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [bcollins@debian.org: bkSVN live]
Posted by cm...@collab.net.
junkio@cox.net writes:
> My understanding was that renames are shown by "(from /original/path:rev)"
> in "svn log -v" output, so I was expecting to see something like:
>
> D /trunk/drivers/ide/aec62xx.c
> ...
> A /trunk/drivers/ide/pci/aec62xx.c (from /trunk/drivers/ide/aec62xx.c:1)
Your understanding is correct. It would appear that renames are
handled strictly as deletes and adds (without copy history) in the
mirroring code.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [bcollins@debian.org: bkSVN live]
Posted by ju...@cox.net.
>>>>> "BC" == Ben Collins <bc...@debian.org> writes:
BC> Thanks to Larry, the bkSVN repo is now live. It's actually bkcvs2svn,
BC> since I am using bkcvs's metadata. However subversion is able to make
BC> better use of the metadata than CVS can. You can get better log output,
BC> for one. Also, you can more easily determine the scope of a change,
BC> since subversion supports changesets.
This is *wonderful*. Thanks for setting up the machinery (and
thanks Larry for hosting).
I have one question. Does the mirror repository track renames?
For example, during linux-2.4 bunch of files were moved from
drivers/ide to drivers/ide/pci. In the mirror, rev 2183 renames
drivers/ide/aec62xx.c to drivers/ide/pci/aec62xx.c. The output
from "svn log" seems to indicate that the mirror repository does
not know about the rename:
$ svn log -r2183 -v \
svn://kernel.bkbits.net/linux-2.4/trunk/drivers/ide/pci/aec62xx.c
------------------------------------------------------------------------
rev 2183: alan | 2002-12-05 07:04:33 -0800 (Thu, 05 Dec 2002) | 9 lines
Changed paths:
M /trunk/drivers/ide/Config.in
M /trunk/drivers/ide/Makefile
D /trunk/drivers/ide/aec62xx.c
D /trunk/drivers/ide/ali14xx.c
...
A /trunk/drivers/ide/pci/adma100.h
A /trunk/drivers/ide/pci/aec62xx.c
A /trunk/drivers/ide/pci/aec62xx.h
...
M /trunk/include/linux/ide.h
[PATCH] -ac IDE merge
This will show a few initial troubles I'm sure.
IDE backport from 2.5
Andre Hedrick, Jens Axboe, Mark Lord, me, and a few others
BKrev: 3def6b01w5m1AHONE_DMfDIgVvf3XA
------------------------------------------------------------------------
My understanding was that renames are shown by "(from /original/path:rev)"
in "svn log -v" output, so I was expecting to see something like:
D /trunk/drivers/ide/aec62xx.c
...
A /trunk/drivers/ide/pci/aec62xx.c (from /trunk/drivers/ide/aec62xx.c:1)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [bcollins@debian.org: bkSVN live]
Posted by Ben Collins <bc...@debian.org>.
On Sun, Jun 15, 2003 at 12:18:40PM -0400, Stefan Monnier wrote:
> > Thanks to Larry, the bkSVN repo is now live. It's actually bkcvs2svn,
>
> All nice and dandy, but you don't say what it is.
> It sounds like it's a Subversion repository that has a copy of the content
> of the BitKeeper repository of Linux and is updated on a regular basis.
> Is that right ?
> Is the update done by a nightly script, or is it done on-the-fly for
> every commit to the BitKeeper repository ?
> Are all branches reflected in the Subversion tree ?
> Is the update going in the other direction as well (so you can commit
> to the BitKeeper repository via the Subversion repository) ?
It's nothing but a mirror of the bkCVS repo in SVN. It serves the same
purpose as bkCVS, which is to allow people who don't want to use bk, or
can't use bk, to track linux 2.4 and linux 2.5 development, between
major releases.
Script is run hourly, 30 minutes offset from the bkcvs scripts. Tags are
tracked. You'd have to understand BK's model to understand why branches
are not there.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [bcollins@debian.org: bkSVN live]
Posted by Stefan Monnier <mo...@rum.cs.yale.edu>.
> Thanks to Larry, the bkSVN repo is now live. It's actually bkcvs2svn,
All nice and dandy, but you don't say what it is.
It sounds like it's a Subversion repository that has a copy of the content
of the BitKeeper repository of Linux and is updated on a regular basis.
Is that right ?
Is the update done by a nightly script, or is it done on-the-fly for
every commit to the BitKeeper repository ?
Are all branches reflected in the Subversion tree ?
Is the update going in the other direction as well (so you can commit
to the BitKeeper repository via the Subversion repository) ?
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [bcollins@debian.org: bkSVN live]
Posted by Ben Collins-Sussman <su...@collab.net>.
Ben Collins <bc...@debian.org> writes:
> Now, finally the SVN URL's:
>
> svn://kernel.bkbits.net/linux-2.4
>
> svn://kernel.bkbits.net/linux-2.5
Wow! Way cool!
$ svn ls -v svn://kernel.bkbits.net/linux-2.5/trunk
_ 10363 rusty 84198 May 26 18:59 CREDITS
_ 10977 vojtech 0 Jun 21 11:17 Documentation/
_ 10850 akpm 47594 Jun 11 22:40 MAINTAINERS
_ 10963 torvalds 29837 Jun 21 11:17 Makefile
_ 9047 zippel 14419 Apr 04 22:18 README
_ 30 torvalds 2815 Feb 05 12:07 REPORTING-BUGS
_ 11026 torvalds 0 Jun 21 11:18 arch/
_ 10632 jmorris 0 Jun 04 00:50 crypto/
_ 11025 akpm 0 Jun 21 11:18 drivers/
_ 11024 akpm 0 Jun 21 11:18 fs/
_ 11026 torvalds 0 Jun 21 11:18 include/
_ 10941 chris 0 Jun 13 20:27 init/
_ 10603 akpm 0 Jun 02 19:40 ipc/
_ 11015 akpm 0 Jun 21 11:17 kernel/
_ 10960 torvalds 0 Jun 21 11:17 lib/
_ 11013 akpm 0 Jun 21 11:17 mm/
_ 11016 akpm 0 Jun 21 11:17 net/
_ 10960 torvalds 0 Jun 21 11:17 scripts/
_ 10943 chris 0 Jun 13 20:27 security/
_ 11023 akpm 0 Jun 21 11:18 sound/
_ 8430 torvalds 0 Mar 17 00:33 usr/
$ svn log -v -r 9000 svn://kernel.bkbits.net/linux-2.5
------------------------------------------------------------------------
rev 9000: akpm | 2003-04-03 10:26:58 -0600 (Thu, 03 Apr 2003) | 9 lines
Changed paths:
M /trunk/mm/shmem.c
[PATCH] tmpfs 1/6 use generic_write_checks
From: Hugh Dickins <hu...@veritas.com>
Remove the duplicated checks in shmem_file-write(), use
generic_write_checks() instead.
BKrev: 3e8c60d29H9Np1KLck9523BBAEleiw
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [bcollins@debian.org: bkSVN live]
Posted by Ben Collins <bc...@debian.org>.
Now, you too can make your own local bk repo, and also stress test your
svn setup :)
The script is based heavily off of cvs2svn, but is trimmed down a lot.
bkCVS allows you to take some things for granted, and adds a little bit
of logic to the madness. Not only that, but this script is meant to run
incrementally.
This option:
-r REV skip output until this revision
Is meant to save an existing repo when something happens to the state
db's (the tree and revision tracking).
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
Re: [bcollins@debian.org: bkSVN live]
Posted by David Summers <da...@summersoft.fay.ar.us>.
On Sun, 15 Jun 2003, Ben Collins wrote:
> svn://kernel.bkbits.net/linux-2.4
>
> svn://kernel.bkbits.net/linux-2.5
>
Hmmm, I think I just figured out why Linus is so succesful. He is a week
ahead of everyone else! :-)
> [linux-2.5] $ svn log
>
> ------------------------------------------------------------------------
> rev 11026: torvalds | 2003-06-21 11:18:06 -0500 (Sat, 21 Jun 2003) | 29
> lines
[snip
> ------------------------------------------------------------------------
> rev 11025: akpm | 2003-06-21 11:18:05 -0500 (Sat, 21 Jun 2003) | 8
> lines
(I assume his CPU clock is just 1 week ahead of everyone else's?
--
David Wayne Summers "Linux: Because reboots are for hardware upgrades!"
david@summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = C0 E0 4F 50 DD A9 B6 2B 60 A1 31 7E D2 28 6D A8
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org