public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@kernel.org>, Junio C Hamano <junio@kernel.org>
To: <linux-kernel@vger.kernel.org>
Cc: <git@vger.kernel.org>
Subject: Moving to BK
Date: Sat, 1 Apr 2006 00:00:00 GMT	[thread overview]
Message-ID: <200604010311.k313BYeS026266@hera.kernel.org> (raw)

We are pleased to announce that both of us will be working for
BitMover Inc., starting this month.

Petr, the author of the popular Cogito front-end for git, will
be modifying Cogito so that it natively works on BK
repositories.  The superior Cogito user interface will
extensively increase added business value of BK by enabling a
variety of innovative workflows for smooth and economical
developer cooperation.

Junio, the current maintainer of git "stupid content tracker",
will first be working on a gateway to import development
histories stored in git into BK.  This move adds value to BK by
freeing the data so far locked in git repositories and making
them available to the BK users.  He may later work on
reimplementing some parts of the git for BK, but it is expected
that there aren't that many.  For example, the "rename
detection" part is not necessary -- BK natively supports rename
tracking, which is a far superiour approach.

There currently is no plan for either of us to be working on the
conversion from BK to git.  There is no technical reason to do
so, and it does not make business sense for BitMover Inc.
either.

- 30 -


             reply	other threads:[~2006-04-01  3:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-01  0:00 Petr Baudis, Junio C Hamano [this message]
2006-04-01  3:14 ` Moving to BK David S. Miller
2006-04-01  3:17   ` Alexander Litvinov
2006-04-01  4:30   ` Linus Torvalds
2006-04-01  6:42     ` Randy.Dunlap
2006-04-01  7:13     ` Jakub Narebski

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=200604010311.k313BYeS026266@hera.kernel.org \
    --to=pasky@kernel.org \
    --cc=git@vger.kernel.org \
    --cc=junio@kernel.org \
    --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