Simon Marlow wrote: > On 27/08/2009 11:18, Sittampalam, Ganesh wrote: >> Simon Marlow wrote: >>>> >>>> I suggest if we stick with the independent repo approach that we >>>> have some automation to check that changes are indeed getting >>>> pushed upstream. >>> >>> Agreed. Can you think of an easy way to automate it? >> >> How about a cronjob that runs >> >> darcs send<upstream-repo> --to=<some-list> >> >> ? > > But the requirement we want is that patches are only pushed upstream, > and never pushed to the branch first.
I might be getting confused about something, but I'd expect this command to send an email with any changes in the branch repo that aren't in upstream. In other words if you have some patches in the branch that aren't upstream, you'll find out and can remedy the situation. Ganesh =============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html =============================================================================== _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
