listhelper-moderate
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

info-cvs post from address@hidden requires approval


From: info-cvs-owner
Subject: info-cvs post from address@hidden requires approval
Date: Thu, 21 Jun 2007 14:40:03 -0400

As list administrator, your authorization is requested for the
following mailing list posting:

    List:    address@hidden
    From:    address@hidden
    Subject: beginner's question on use
    Reason:  Post by non-member to a members-only list

At your convenience, visit:

    http://lists.nongnu.org/mailman/admindb/info-cvs
        
to approve or deny the request.
--- Begin Message --- Subject: beginner's question on use Date: Thu, 21 Jun 2007 11:25:47 -0700 User-agent: G2/1.0
I am not sure if this is the totally right place for the question, so
please redirect me if so.

I am using CVS at work.  The way it is being used bothers me.  We
create a branch 'a' for development.  If a new release is needed to be
made we make a branch 'b'.  If we are still having changes go on for
branch 'a' we post the changes to branch 'a' and branch 'b'.  The
cycle continues where we make make another branch, branch 'c' for
development off of branch 'b'.  This doesn't seem like a responsible
way to use CVS.  No one else on the team knows any better.  What would
be the appropriate way to handle a sequential release cycle?


--- End Message ---
--- Begin Message --- Subject: confirm cdf3bba624bce8bbce5caf601da3f6df0901e947
If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message.  Do this if the message is
spam.  If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list.  The Approved: header can also appear in the first line
of the body of the reply.

--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]