diff options
| author | Stephen Torri <storri@users.sourceforge.net> | 2004-09-16 14:54:25 +0000 |
|---|---|---|
| committer | Stephen Torri <storri@users.sourceforge.net> | 2004-09-16 14:54:25 +0000 |
| commit | 107d3a4a90ab7a645af5832f528ae78a84d2d7d9 (patch) | |
| tree | 4eae7b425c4cd70cf147fa3a86360de7b447a93f /doc | |
| parent | a7f2840fab0afb6886eca39f3272959e3df38dea (diff) | |
| download | xine-lib-107d3a4a90ab7a645af5832f528ae78a84d2d7d9.tar.gz xine-lib-107d3a4a90ab7a645af5832f528ae78a84d2d7d9.tar.bz2 | |
Updated configure.ac version
Updated HOWTO to reflect incorrect cvs tag command. A -r is means to have a particular version in mind when tagging while -R means to recursively tag all files with a given tag name.
CVS patchset: 6975
CVS date: 2004/09/16 14:54:25
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/internal/HOWTO.release | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/internal/HOWTO.release b/doc/internal/HOWTO.release index 3827b2dba..977ac208d 100644 --- a/doc/internal/HOWTO.release +++ b/doc/internal/HOWTO.release @@ -93,7 +93,7 @@ Currently, best practice to get a release out looks like this: The tests have now all passed. you've got the release tarball in your hands. -7) Tag the release: cvs tag -r xine-1_2_3-release +7) Tag the release: cvs tag -R xine-1_2_3-release (this would be the tag for xine-lib-1.2.3, for example) 8) upload the tarball to ftp:/upload.sf.net/incoming |