Thanks for the comments! >>>>> "Rich" == Richard Lowe <richlowe at richlowe.net> writes:
>> We will generate per-putback emails, as we do today with TeamWare. >> The format will be slightly different. In particular, renames will >> appear as a list of deleted files and a separate list of created >> files. Rich> This is true, but does not *have* to be true, it's just a matter Rich> of how that code was written (you could do the same stuff cdm Rich> does, and get the same info, if you wished). Okay, I'll adjust the wording. >> It is also possible to view the changes to the gate using "hg log". >> Unlike "sccs prt", this command shows changes across the entire >> repository, not just for a single file. Rich> You can specify a filename to hg log, just as you would with prt, Rich> you can also specify that you want to follow that history across Rich> renames/copies, and various other things. Rich> The way you've written that makes it seem like you have to see the Rich> entire log across the whole gate, you don't. I'll adjust the wording. >> Mercurial does not keep a per-putback history file the way that >> TeamWare does. Rich> True, but that's because the *only* history it keeps is, by those Rich> terms, per-putback. But "hg log" cannot tell you information that you can get from a TeamWare history file. In particular, it won't tell you who pushed changes, or when. Should I make this point clearer? >> We have a CR (6639131) to change this, i.e., so that the notification >> email comes from the person doing the putback, but it is not >> currently on our stopper list for the move to Mercurial. Rich> We never fully looked into how we would go about doing that. It's Rich> tempting to suggest we look at the notification extension I added a note about this to 6639131. mike
