Comment 14 for bug 400215
Revision history for this message
| Björn Tillenius (bjornt) wrote Re: [Bug 400215] Re: Merge proposal URLs are ugly and needlessly long | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
On Fri, Dec 10, 2010 at 01:54:55AM -0000, Martin Pool wrote:
> > Tim said: "Despite all this, and whatever our desires may be to avoid
> > people talking about reviews using their number, it'll happen anyway
> > because it is a single number that uniquely identifies a merge proposal
> > / code review."
> >
> > I have never seen this, so if it happens at all, it's probably too rare
> > a case to worry about.
>
> I think there is a chicken and egg: you can't get from the id to the
> mp so people don't use them. Instead, I see people using somewhat
> vague textual descriptions like "my merge refactoring branch". They
> certainly do this with bugs too but at least there they have the
> option to say "do you mean 123456?"
Indeed. Giving the ID today isn't useful, since given that it's
practically impossible to find the review in the web UI. You have to
give a description or branch name, and given that it's actually not that
easy to find the review either.
I would love to be able to say "about MP 1234, ...." on IRC, and then
have a bot giving the details, including a URL to the MP, just like we
have with bugs. I think people would use IDs more that way, and it would
improve usability.
--
Björn Tillenius | https:/