Well at this point in time there is not much point in writing mercurial
scripts. But its something that should be integrated in the git workflow.
Also there isn't a dedicated hg qrefresh-hook as there is for commits,
though that can be hacked around...
On Thursday, January 31, 2013 10:42:25 AM UTC, Jeroen Demeyer wrote:
>
> On 2013-01-31 11:36, Volker Braun wrote:
> > On Thursday, January 31, 2013 10:31:16 AM UTC, Jeroen Demeyer wrote:
> >
> > I'd like to mention that in the release management script, there are
> a
> > few things that I check for, such as:
> >
> > * no bare "except:" without exception class
> > * no TABs
> > * no use of AssertionError ("assert" is fine, but not "except
> > AssertionError" for example)
> >
> >
> > And thats great, but its the wrong place to check. The patch author
> > should be immediately notified if his/her patch fails the automated
> > checks, not weeks or months later.
> Fair enough, if you know how to implement such a "commit hook", feel
> free to do so...
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
