Re: Discourage cvs-import

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

 



On 22.02.2007 22:05, Warren Togami wrote:
Thorsten Leemhuis wrote:
John Dennis schrieb:
Please at least don't break cvs-import.sh for non-initial commits.  It's
_way_ more pleasant to use when updating tarballs than make upload or
make new-source.
+1
cvs-import is the most sane way to update an rpm when we are upstream.
There are quite a few rpm's for which we are the upstream and importing
into 'dist cvs' is just the final step after preparing a new release. I
really don't want some tool forcing me to review the changes I just made
to make sure I approve of my own work.
It seems it wasn't clear in my mail: cvs-import.sh would still be there,
just not documented in the wiki. So those that know about it can just
continue to use it.
Not documented in the Wiki even for initial imports?

Well, that would be counter-productive. ;-) So no, it should be documented; probably something like this "use cvs-import.sh for the initial import like this [...]; Updating the package later work like this [...] cvs update[...] cvs diff [...]cvs commit [...]"

CU
thl

--
Fedora-maintainers mailing list
Fedora-maintainers@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers

--
Fedora-maintainers-readonly mailing list
Fedora-maintainers-readonly@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-maintainers-readonly

[Index of Archives]     [Fedora Users]     [Fedora Development]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux