linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrea Arcangeli <andrea@suse.de>
To: Dave Jones <davej@codemonkey.org.uk>,
	Andrew Morton <akpm@digeo.com>,
	lm@bitmover.com, linux-kernel@vger.kernel.org
Subject: Re: 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c
Date: Wed, 5 Feb 2003 21:06:31 +0100	[thread overview]
Message-ID: <20030205200631.GK19678@dualathlon.random> (raw)
In-Reply-To: <20030205194257.GA17922@codemonkey.org.uk>

On Wed, Feb 05, 2003 at 07:42:57PM +0000, Dave Jones wrote:
> On Wed, Feb 05, 2003 at 07:45:35PM +0100, Andrea Arcangeli wrote:
> 
>  > I can't yet fetch a full tree out of bitkepper yet (you know the network
>  > protocol must be reverse engeneered first), I can only fetch
>  > incrementals with metadata and raw patch so far because this is the
>  > thing I care about most, after I've all the changesets in live form in
>  > my db I don't mind too much about the ability to checkout a the whole
>  > tree too, since I can do the same starting from my open db rather than
>  > using the proprietary one.
> 
> Why not save effort, and just grab from http://ftp.kernel.org/pub/linux/kernel/v2.5/testing/cset/

I used them so far, but they're as useless as the patches mailing list
for my purposes, first they're not useful to checkout a tree, the order of
the changesets I mean, and they don't tell when a certain kernel revision
matches a changeset, I'm checking out Linus's tree with it, they don't
provide live metadata easy to browse in software, to monitor in
background automatically, I need to see all the evolution of a certain
file or subsystem with all the metadata and raw patches with a few lines
of python, and last but not the least I like it to run in real time w/o
delays.

In short I'm extracting the whole database and I'm storing it in an open
form so I can manipulate it as I need. I don't watch branches, I only
fetch the main branch.

This makes very trivial also to checkin the whole thing into another
version control system and to keep it uptodate in background even if
this isn't my purpose.

I don't think it's worthwhile to do more than that on the bk side, I
mean, it's not an openbitkepper thing, I would rather write something
from scratch rather than reverse engeneering the whole thing just to
provide compatibility, once you've all the info in open form, you can
use it as a transient format that allows you to fill it into any other
project.

What matters to me is only the info and the easiest way to manipulate it
in software, it's much more powerful than what bitkeeper can do this way
because I program it, downside is that I need some more disk space ;).

Andrea

  reply	other threads:[~2003-02-05 19:57 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-05 17:40 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c Andrea Arcangeli
2003-02-05 18:23 ` Andrew Morton
2003-02-05 18:45   ` Andrea Arcangeli
2003-02-05 19:42     ` Dave Jones
2003-02-05 20:06       ` Andrea Arcangeli [this message]
2003-02-05 19:43     ` Andrew Morton
2003-02-05 19:51       ` Andrea Arcangeli
2003-02-05 20:09         ` Andrew Morton
2003-02-05 20:18           ` Andrea Arcangeli
2003-02-05 20:33             ` Andrew Morton
2003-02-05 23:29         ` Larry McVoy
2003-02-05 20:11       ` Matt Reppert
2003-02-05 20:24         ` Andrea Arcangeli
2003-02-05 20:56           ` Linus Torvalds
2003-02-05 20:25         ` Linus Torvalds
2003-02-05 23:31         ` Larry McVoy
2003-02-05 23:37           ` Christoph Hellwig
2003-02-05 23:57             ` Larry McVoy
2003-02-06  0:22               ` Robert Love
2003-02-06 16:58               ` Andreas Dilger
2003-02-06 17:30                 ` Larry McVoy
2003-02-06 17:55                   ` Matt Reppert
2003-02-07 16:18                     ` glibc-2.3 [Was: Re: 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c] Horst von Brand
2003-02-07 18:06                       ` Larry McVoy
2003-02-06  0:37           ` 2.5 changeset 1.952.4.2 corrupt in fs/jfs/inode.c Chris Funderburg (at home)
2003-02-06  0:45           ` Alan Cox
2003-02-05 23:51             ` Larry McVoy
2003-02-06  0:02               ` Mitch Adair
2003-02-06  0:08                 ` Larry McVoy
2003-02-06 10:02           ` Nick Craig-Wood
2003-02-09 18:37             ` Kenneth Johansson
2003-02-05 19:46 ` Sam Ravnborg
2003-02-05 20:04 ` Dave Kleikamp
2003-02-05 20:10   ` Andrea Arcangeli
2003-02-05 20:16     ` Dave Kleikamp
2003-02-05 20:34     ` Sam Ravnborg
2003-02-05 20:51       ` Andrea Arcangeli
2003-02-05 22:09         ` Linus Torvalds
2003-02-06 10:46           ` Roman Zippel
2003-02-06 11:09           ` Andreas Schwab
2003-02-05 21:56     ` Linus Torvalds
2003-02-07 14:56 ` Pavel Machek
2003-02-08 18:28   ` Larry McVoy
2003-02-08 19:36     ` Martin J. Bligh
2003-02-09 10:57     ` Pavel Machek
2003-02-09 14:15       ` Andrea Arcangeli
2003-02-13  1:50     ` Jamie Lokier
2003-02-13  1:57       ` Jamie Lokier

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=20030205200631.GK19678@dualathlon.random \
    --to=andrea@suse.de \
    --cc=akpm@digeo.com \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    /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;
as well as URLs for NNTP newsgroup(s).