Modify ↓
Opened 16 years ago
Last modified 4 years ago
#8068 new enhancement
Mercurial bundle attachments should be viewable in readable representation.
Reported by: | fvbommel | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Milestone: | plugin - mercurial |
Component: | plugin/mercurial | Version: | none |
Severity: | normal | Keywords: | bundle mimeview |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When a mercurial bundle is attached to a ticket, viewing that attachment should show a readable representation of the changesets it contains (as if a regular patch had been attached).
Extra points if it also shows metadata about the revisions in the bundle, like author and commit message :).
(All of the above assumes the project has a mercurial repository and the parent revision of the bundle is in that repository)
Attachments (0)
Change History (2)
comment:1 by , 16 years ago
Keywords: | bundle mimeview added |
---|---|
Milestone: | → not applicable |
comment:2 by , 15 years ago
Milestone: | not applicable → mercurial-plugin |
---|
Note:
See TracTickets
for help on using tickets.
Interesting suggestion, I'll have a look.
One of the problem I see is that a bundle is not always like a "patch", i.e. it's a repository on its own, so it can actually contain several branches, merges, etc.
So it should eventually be possible to show a bundle as a patch only if there's one head in the bundle and one common ancestor of the revisions from the bundle in the repository.
Another approach would be to open the bundle as an actual repository, allowing the full range of browsing operations on it (that would be based on the MultiRepos branch).