[7845] in SIPB bug reports
Re: Bitkeeper installed in the SIPB locker
daemon@ATHENA.MIT.EDU (Theodore Tso)
Tue Sep 25 14:32:16 2001
Date: Tue, 25 Sep 2001 14:30:32 -0400
From: Theodore Tso <tytso@MIT.EDU>
To: Greg Hudson <ghudson@mit.edu>
Cc: Theodore Tso <tytso@mit.edu>, bug-sipb@mit.edu
Message-ID: <20010925143032.A575@thunk.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200109191442.KAA13788@egyptian-gods.MIT.EDU>; from ghudson@MIT.EDU on Wed, Sep 19, 2001 at 10:42:55AM -0400
On Wed, Sep 19, 2001 at 10:42:55AM -0400, Greg Hudson wrote:
> > If you have any questions, please let me know.
>
> Is it clear to end users that all of their bitkeeper commits will be
> sent off to openlogging.org?
Yes, when you set up a repository, or the first time a user tries to
commit to a bitkeeper that is using open logging, bitkeeper explicitly
notifies you that the commits will be sent off to openlogging.org, and
the user has the option of aborting the commit if he/she doesn't want
the changelogs going to the openlogging server.
I'll note when you commit a file to sourceforge for the first time
using CVS, you don't get any warning that your changelogs plus code
diffs will be made available to everyone using a cvsweb interface,
although granted that may be more obvious given that the CVS
repository itself is located on sourceforge.
- Ted
