This can be used to inspect the generated pattern, but also to benchmark
the time it takes to parse hgignore.
Details
- Reviewers
Alphare - Group Reviewers
hg-reviewers - Commits
- rHG6d4daf51283c: rhg: implement the debugignorerhg subcommand
Diff Detail
- Repository
- rHG Mercurial
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
I'll look at these patches and take them after 6.0 is out (this includes the one I've already accepted). It's been delayed quite a bit due to Windows issues.
Thanks for waiting for so long. 6.0 is out (it was delayed a lot for Windows reasons), so I'll be back to reviewing patches for default.
rust/hg-core/src/matchers.rs | ||
---|---|---|
602 | It would be nice to have a type alias for this (and the one below). We already have one in hg-core/src/dirstate/status.rs, probably should be refactored. | |
rust/rhg/src/commands/debugignorerhg.rs | ||
18 | nit: we prefer new commands to have dashes in them now, but it's really not a big deal since this is temporary anyway |
rust/rhg/src/commands/debugignorerhg.rs | ||
---|---|---|
18 | Ah right, we'd need a smarter macro, this is well out of scope |
@Alphare, folded commit seems better than the separate ones in this case, though, since the second commit is simply incorporating review comments, not really an independent change.
I ran hg fold --from .^ followed by hg phabsend . to make this less confusing.
If you were thinking of a certain logical split of this commit into two that I'm not aware of, please let me know.
Sure, most of the time, changes can be incorporated into the same changeset, but for ones that move a lot of code around (like refactor suggestions), we usually like to split them. This has a two-fold advantage of making the review of the actual change more obvious, and to make sure a mistake didn't appear in the refactor.
In this case, I should have been more explicit: I saw two concatenated commit messages and figured you already had two changesets, so I asked you to send them as separate.
Basically: one changeset == one phab diff
@Alphare, Ok. I understood you before, but those commits were not suitable for independent submission.
I only have one commit now. Would you like me to split something out into a separate commit?
Yes, I think in this case a separate changeset for the type refactor (of the old code) would make sense.
Also I was sure I added a comment about the println! usage, but I must have forgotten!
rust/rhg/src/commands/debugignorerhg.rs | ||
---|---|---|
38 | This should use ui.write_stdout, which would also remove the need for the potentially lossy utf8 conversion. |
It would be nice to have a type alias for this (and the one below). We already have one in hg-core/src/dirstate/status.rs, probably should be refactored.