On Thu, Sep 20, 2007 at 08:12:51AM +0200, Jim Meyering wrote:
> Paul Eggert <[EMAIL PROTECTED]> wrote:
> > Jim Meyering <[EMAIL PROTECTED]> writes:
> >> I'll turn off cvs soon, probably tomorrow.
> >
> > By "turn off cvs" do you mean to disable even read-only access to old
> > versions?
>
> No, of
Jim Meyering <[EMAIL PROTECTED]> writes:
> You don't mind the "cvs diff" delays?
No. I don't do it very often.
> It's easy to move such trees to git.
OK, but I have dozens of them and don't want to wade through them all
right now. I wouldn't be surprised if others have such trees too.
> So,
Eric Blake byu.net> writes:
> $ git checkout -b cvs-branch cvs-readonly
...
> $ git branch
> * cvs-readonly
> master
Excuse my typo (that's what I get for retyping instead of screen capture).
The branch name should appear as cvs-branch, not as a copy of the cvs-readonly
tag.
git lets you hav
Paul Eggert CS.UCLA.EDU> writes:
>
> Jim Meyering meyering.net> writes:
>
> > I'll turn off cvs soon, probably tomorrow.
>
> By "turn off cvs" do you mean to disable even read-only access to old
> versions? I hope not; I still have a bunch of old source trees,
> checked out from CVS, that I
Paul Eggert <[EMAIL PROTECTED]> wrote:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>> I'll turn off cvs soon, probably tomorrow.
>
> By "turn off cvs" do you mean to disable even read-only access to old
> versions?
No, of course not.
Just as checking the box added "GIT" to some web menus,
I presume
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 9/19/2007 5:26 PM:
> Jim Meyering <[EMAIL PROTECTED]> writes:
>
>> I'll turn off cvs soon, probably tomorrow.
>
> By "turn off cvs" do you mean to disable even read-only access to old
> versions? I hope not; I still have
Jim Meyering <[EMAIL PROTECTED]> writes:
> I'll turn off cvs soon, probably tomorrow.
By "turn off cvs" do you mean to disable even read-only access to old
versions? I hope not; I still have a bunch of old source trees,
checked out from CVS, that I occasionally need to do a "cvs diff" on.
Jim Meyering meyering.net> writes:
> > I'd like to commit this, once Bruno's patch is included (partly, to make
sure
> > that git push privileges work).
>
> Go for it.
The commit worked, so it looks like the user permissions have been carried over
from CVS.
I found that adding the following
Jim Meyering <[EMAIL PROTECTED]> wrote:
> I've just added a commit hook to disable commits to
> gnulib's CVS repository.
>
> Now, any attempt to commit via cvs gives this:
>
> $ cvs ci -m. ChangeLog
> You may not commit here anymore. Use git.
> cvs commit: Pre-commit check failed
>
Eric Blake <[EMAIL PROTECTED]> wrote:
> Jim Meyering meyering.net> writes:
>> I've just added a commit hook to disable commits to
>> gnulib's CVS repository.
>
> There's one more commit that needs to be imported:
> http://cvs.savannah.gnu.org/viewvc/gnulib/ChangeLog?root=gnulib&r1=1.1938&r2=1.1939
Jim Meyering meyering.net> writes:
>
> I've just added a commit hook to disable commits to
> gnulib's CVS repository.
>
There's one more commit that needs to be imported:
http://cvs.savannah.gnu.org/viewvc/gnulib/ChangeLog?
root=gnulib&r1=1.1938&r2=1.1939
before we can start open commits into
I've just added a commit hook to disable commits to
gnulib's CVS repository.
Now, any attempt to commit via cvs gives this:
$ cvs ci -m. ChangeLog
You may not commit here anymore. Use git.
cvs commit: Pre-commit check failed
cvs [commit aborted]: correct above errors first!
[
12 matches
Mail list logo
