Date: 11/06/99
- Next message: kk: "[PHPLIB-DEV] cvs commit"
- Previous message: kk: "[PHPLIB-DEV] cvs commit"
- In reply to: Jesse Swensen: "[PHPLIB-DEV] Is there a FAQ or HOWTO"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Nov 06, 1999 at 12:06:21PM -0500, Jesse Swensen wrote:
> I have some changes I would like to contribute. As this is my first time
> doing this, is there a FAQ or HOWTO? I am uncertain how to get my changes
> implemented.
Get the most current version of the file COMMIT.
When and where to commit:
0. Are you subscribed to phplib-dev <email protected>?
Yes: Go ahead.
No: Subscribe now or go home. All development discussion is
going on on that list. If you are not on that list, you
should not commit.
1. Do you have a cvs write account?
Yes: Are your changes compatible?
Yes: Commit into the distribution, that is, into php/ and pages/.
Try to avoid creating new directories.
Committing into the distribution is the best way to get your
changes tested. If your changes aren't good, it is also a
good way to get flamed.
No: Discuss the issue on the list. If there are objections or there
is a veto by me, get the issue cleared or commit into the
unsup/ directory. Stuff in unsup/ is there because it has
issues that are to be resolved or because it is orphaned.
No: Make sure you get the very latest CVS version, by either
using the cvsread account or the CVS web interface at
http://phplib.netuse.de/cgi/cvsweb.cgi.
Make sure your changes are against the latest version of
these files. Send a diff as a MIME file attachment to
the phplib-dev list or get a CVS committer to accept your
patch.
2. Did you update the CHANGES file?
Yes: Good.
No: You are toast.
3. Did you update the documentation?
Yes: Good.
No: You better have a good excuse (like: "I promise to update
the docs within the next 7 days").
---------------------------------------------------------------------------
Working with the CVS:
1. Logging in and checking out:
$ cd ~/Source
$ cvs -d :pserver:cvsread <email protected>:/repository login
Password: cvsread
$ cd ~/Source
$ cvs -d :pserver:cvsread <email protected>:/repository checkout php-lib
If you have a CVS write account, use your CVS write account name
to log in instead of cvsread.
2. Updating to the most current version:
$ cd ~/Source/php-lib
$ cvs update -dAP
3. Committing changes:
$ cd ~/Source/php-lib
$ cvs update -dAP
$ cvs commit
4. Diffing your changes against the current CVS to see what you
changed:
$ cd ~/Source/php-lib
$ cvs diff -u
5. Diffing two versions of a file:
$ cd ~/Source/php-lib
$ cvs diff -u -r 1.3 COMMIT
6. Seeing which labels are assigned to a file
$ cd ~/Source/php-lib
$ cvs status -v CHANGES
-
PHPLIB Developers Mailing List. Send messages to <phplib-dev <email protected>>.
To unsubscribe, send "unsubscribe" to <phplib-dev-request <email protected>> in
the body, not the subject, of your message.
- Next message: kk: "[PHPLIB-DEV] cvs commit"
- Previous message: kk: "[PHPLIB-DEV] cvs commit"
- In reply to: Jesse Swensen: "[PHPLIB-DEV] Is there a FAQ or HOWTO"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

