Re: Suggestion for cvs tag handling

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

 



On Fri March 7 2008, Toshio Kuratomi wrote:
> 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'.

Thanks, here is an example how to perform such a check with python:
http://till.fedorapeople.org/cvs-status-check.py

In case python scripts are allowed in the commons directory, I can write a 
patch for Makefile.common that will use it.

Regards,
Till

Attachment: signature.asc
Description: This is a digitally signed message part.

-- 
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