Merge lp:~jml/launchpad/link-to-lp-revision into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | Brad Crittenden on 2010-07-30 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 11273 |
| Proposed branch: | lp:~jml/launchpad/link-to-lp-revision |
| Merge into: | lp:launchpad |
| Diff against target: |
15 lines (+4/-1) 1 file modified
lib/lp/app/templates/base-layout-macros.pt (+4/-1) |
| To merge this branch: | bzr merge lp:~jml/launchpad/link-to-lp-revision |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| Brad Crittenden (community) | code | 2010-07-29 | Approve on 2010-07-30 |
|
Review via email:
|
|||
Description of the Change
This branch changes the footer on edge to link to the Launchpad stable branch.
The way I've done the change is kind of crappy. I welcome suggestions on how to do it better.
| Jonathan Lange (jml) wrote : | # |
On Fri, Jul 30, 2010 at 3:21 PM, Brad Crittenden <email address hidden> wrote:
> Review: Needs Information code
> Hi Jono,
>
> I don't have any suggestions for doing it better. But I wonder why you want a link to the branch here to the stable branch instead of to the devel branch or even https:/
The devel branch has very little to do with what's on edge, and is to
my mind merely a convenient mechanism for queueing up changes to the
stable branch. To put it another way, why would we link to broken code
when we can link to a known-good branch?
I don't link to Getting because part of the motivation for the link is
to make it easy to see a revision log. I don't know whether that's a
good enough reason.
Thanks for the review.
jml

Hi Jono,
I don't have any suggestions for doing it better. But I wonder why you want a link to the branch here to the stable branch instead of to the devel branch or even https:/ /dev.launchpad. net/Getting