From: Duncan C. <dun...@wo...> - 2006-01-10 17:49:54
|
On Tue, 2006-01-10 at 17:27 +0000, Axel Simon wrote: > On Tue, 2006-01-10 at 16:00 +0000, Duncan Coutts wrote: > > So I've got the darcs repo set up so that it emails the gtk2hs-commit > > list whenever anyone "darcs push"es. > > > > I've made another change from what you see below, which is that I make > > it include the full patch and not just the summary. > > > > Note that we will get one email per-push not one per-patch, that is if > > you record several patches and push them all at once then only one email > > will be delivered but it should include details of all the patches. > > Ok. So I assume I push logical changes together to make commit messages > easier to read. The logical unit of change in darcs is the patch, which you get using darcs record. How patches are propagated between repos is not important. So the answer is that you don't need to do that. It's not really important. If it'd make it easier I could see if I could make it send and email per-patch rather than per-push (it's easier to do it the way it is now since the script gets invoked once per-push but it should be possible to iterate through the patches and send an email for each one). > So now I could go off and work on gtk2hs again?! ... Yep. Yay! :-) Duncan |