rpms/mlt/devel .cvsignore, 1.4, 1.5 mlt.spec, 1.4, 1.5 sources,
1.4, 1.5
Michael Schwendt
mschwendt at gmail.com
Fri Dec 11 12:16:25 CET 2009
- Previous message: rpms/mlt/devel .cvsignore, 1.4, 1.5 mlt.spec, 1.4, 1.5 sources,
1.4, 1.5
- Next message: rpms/mlt/devel .cvsignore, 1.4, 1.5 mlt.spec, 1.4, 1.5 sources,
1.4, 1.5
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
On Fri, 11 Dec 2009 12:07:57 +0100, Dominik wrote:
> On Friday, 11 December 2009 at 12:04, Zarko Pintar wrote:
> > When I'm using this procedure for updates then I have some tagging issues.
>
> What tagging issues?
All "tagging issues" after plain cvs commit based updates are _user errors_.
For example, working with an out-of-date "common" checkout (which contains
an old "branches" file).
The only issue cvs-import.sh works around is that because it creates
a fresh temporary check-out, it always checks out a fresh "branches"
file. But that's only a corner-case after "devel" was branched to
its own directory.
cvs-import.sh does not and cannot work around other ordinary "tagging
issues", which are based on user's mistakes.
Really, do avoid using cvs-import.sh for updates. Prefer plain cvs.
- Previous message: rpms/mlt/devel .cvsignore, 1.4, 1.5 mlt.spec, 1.4, 1.5 sources,
1.4, 1.5
- Next message: rpms/mlt/devel .cvsignore, 1.4, 1.5 mlt.spec, 1.4, 1.5 sources,
1.4, 1.5
- Messages sorted by:
[ date ]
[ thread ]
[ subject ]
[ author ]
More information about the rpmfusion-developers
mailing list