pascal.quantin at free.fr
Mon Jun 20 14:04:13 CDT 2011
Le 20/06/2011 20:58, Augie Fackler a écrit :
> On Mon, Jun 20, 2011 at 1:41 PM, Felix Dorner <fdorner at tuenti.com> wrote:
>> Hi Kevin,
>> On Mon, Jun 20, 2011 at 6:17 PM, Kevin Bullock
>> <kbullock+mercurial at ringworld.org> wrote:
>>> Bookmarks aren't designed to do this.
>> Yes. I didn't feel it's a good idea either.
>>> Tags are created with commits because this makes them auditable in the same way that the rest of the project history is auditable. An alternate design would put tags in a > parallel history (i.e., their own revlog—and this has been discussed to death here and on -devel), but that's not the design choice that was made.
>> Say I follow the (good?) practice and the tagging changesets only
>> affect .hgtags, no other files. What would be a good way to filter
>> them out from the history? What I'd need is a hg log that shows me all
>> changesets except the ones that only modified .hgtags. And also the
>> inverse: A log of all changesets that affect .hgtags and only .hgtags.
>> I bet there's an easy one :)
> hg log -r 'not modifies(.hgtags)'
This command will not hide the first tag adding the .hgtags file. hg log
-r "not filelog(.hgtags)" seems to filter all of them.
More information about the Mercurial