• Bug#265810: cvs update should put default server in new directories' CV

    From Miciah Dashiel Butler Masters@1:229/2 to All on Sun Aug 15 08:00:12 2004
    From: [email protected]

    Package: cvs
    Version: 1.12.9-3
    Severity: wishlist

    I have a shell function, cvsup, that gives cvs the -d option to specify
    a mirror; I keep the master server in **/CVS/Root. This lets me cvsup
    without hammering the master server, while still allowing cvs diff,
    cvs ci, and so on to function properly.

    When a new directory is created and cvsup creates it,
    CVS puts the mirror in CVS/Root of the new directory:

    % export CVSROOT=:pserver:[email protected]:/var/cvs/elinks
    % cvs login
    % cvs -z9 co -D'2004-08-14 07:53:13' elinks
    [...]
    % unset CVSROOT
    % cd elinks
    % echo ':pserver:[email protected]:/home/cvs/elinks' > **/CVS/Root
    % cvs -d':pserver:[email protected]:/var/cvs/elinks' -z9 up
    % -D'2004-08-14 07:53:14' -dP
    [...]
    cvs update: Updating src/protocol
    P src/protocol/Makefile.am
    P src/protocol/protocol.c
    P src/protocol/protocol.h
    [...]
    cvs update: Updating src/protocol/nntp
    U src/protocol/nntp/Makefile.am
    U src/protocol/nntp/codes.c
    [...]
    % cat src/protocol/CVS/Root
    :pserver:[email protected]:/home/cvs/elinks
    % cat src/protocol/nntp/CVS/Root
    :pserver:[email protected]:/var/cvs/elinks

    src/protocol/nntp is the new directory.

    I would prefer that CVS use CVS/Root of the parent directory
    of the new directory for the new directory's CVS/Root.

    Is there any relevant option which I've missed
    or a problem with the behaviour I desire?

    Love,

    -- Miciah <[email protected]>


    --
    To UNSUBSCRIBE, email to [email protected]
    with a subject of "unsubscribe". Trouble? Contact [email protected]

    --- SoupGate-Win32 v1.05
    * Origin: you cannot sedate... all the things you hate (1:229/2)