Re: Suggestion for cvs tag handling

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

 



Till Maas wrote:
On Fri March 7 2008, Jarod Wilson wrote:

Now, perhaps if there was a pre-commit hook that checked to see that all
referenced Sources and Patches were actually available, and prevent a
checkin w/a new patch referenced in a spec that isn't cvs added, then I
might be less opposed to immutable tagging before building...

Is there a way to do this efficiently with cvs? cvs status seems to open a network connection everytime one runs it, so a cvs status on every file e.g. used in the kernel spec would take forever.

All you need is a single run of 'cvs -n update'.

-Toshio

Attachment: signature.asc
Description: OpenPGP digital signature

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux