Launchpad itself

don't add the full text of the bug description to the mail when the mail already sends the full text

Bug #251501 reported by Scott Kitterman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

I've set the preference to get the full text of bugs with the mail, but I really don't need it twice. Here's an (fixed) example:

[Bug 251395] [NEW] Launchpad front page inaccurate
 Date: Thu Jul 24 02:37:27 2008
 From: Scott Kitterman <email address hidden>
 To: <email address hidden>
 Reply to: Bug 251395 <email address hidden>

Public bug reported:

Currently the front page of Launchpad says:

"# Redesigned pages for bugs, translations, and distributions
We're making Launchpad easier to navigate."

This is incorrect and should be removed. Virtually all people I've seen
comment on the new layout have complained about it being more difficult.

** Affects: launchpad
     Importance: Undecided
         Status: New

--
Launchpad front page inaccurate
https://bugs.launchpad.net/bugs/251395
You received this bug notification because you are a direct subscriber
of the bug.

Status in Launchpad itself: New

Bug description:
Currently the front page of Launchpad says:

"# Redesigned pages for bugs, translations, and distributions
We're making Launchpad easier to navigate."

This is incorrect and should be removed. Virtually all people I've seen comment on the new layout have complained about it being more difficult.
     2.5.1-2ubuntu1 0
        500 http://de.archive.ubuntu.com hardy/main Packages

See original description
Tags: bugs email
Revision history for this message
Scott Kitterman (kitterman) wrote :

Acutally that's not a good example. I'll include one the next time it happens.

Scott Kitterman (kitterman)
description: updated
Matthew Paul Thomas (mpt)
Changed in launchpad:
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Marius Kruger (amanica) wrote :

I don't know why Scott says its not a good example, but in any case it happens to me too.
Thanks to this bug report I now know I can disable descriptions in all bug mails, which I did.

Another example:
=======
Public bug reported:

While testing stacked branches, I wanted to skip the working-tree
creation, so I created a shared repo with --no-trees.

When doing so, it created its own standalone repository, rather than re-
using the local one, which also caused it to build a working tree.

I then tried just removing newbranch/.bzr/repository and I started
getting failures:

$ time bzr branch stacked/ unstacked --lsprof-file branch_stacked.txt
bzr: ERROR: The branch stacked/ has no revision None.

Which is strange, considering there are 0 pack files in the standalone
location. I certainly would have thought that the standard open commands
would find the shared location.

** Affects: bzr
    Importance: Undecided
        Status: New

--
stacked branches don't use shared repository
https://bugs.launchpad.net/bugs/301739
You received this bug notification because you are subscribed to Bazaar.

Status in Bazaar Version Control System: New

Bug description:
While testing stacked branches, I wanted to skip the working-tree creation, so I created a shared repo with --no-trees.

When doing so, it created its own standalone repository, rather than re-using the local one, which also caused it to build a working tree.

I then tried just removing newbranch/.bzr/repository and I started getting failures:

$ time bzr branch stacked/ unstacked --lsprof-file branch_stacked.txt
bzr: ERROR: The branch stacked/ has no revision None.

Which is strange, considering there are 0 pack files in the standalone location. I certainly would have thought that the standard open commands would find the shared location.

Revision history for this message
Graham Binns (gmb) wrote :

Marius, can you post the headers of the offending bugmail please? It may help us to diagnose where things are going wrong.

Revision history for this message
Graham Binns (gmb) wrote :

Marking this incomplete, pending email headers.

Changed in malone:
status: Confirmed → Incomplete
Revision history for this message
Martin Pool (mbp) wrote :

I've been getting this too; it looks really silly when people have posted a long trackeback in the description.

Changed in malone:
status: Incomplete → New
Revision history for this message
Martin Pool (mbp) wrote :
Revision history for this message
Martin Pool (mbp) wrote :

What's interesting is that contrary to Scott's original report, my preference for "Include bug descriptions when sending me bug notifications" in <https://edge.launchpad.net/~mbp/+edit> is *not* checked!

Graham Binns (gmb)
Changed in malone:
status: New → Triaged
Revision history for this message
Martin Pool (mbp) wrote :

I filed bug 396364 for the fact that the switch that should turn this off apparently does not.

Graham Binns (gmb)
tags: added: story-better-bug-notification
Graham Binns (gmb)
tags: added: story-better-notification-sending
Gary Poster (gary)
tags: removed: story-better-bug-notification
Curtis Hovey (sinzui)
Changed in launchpad:
importance: Medium → Low
tags: added: bugs email
removed: lp-bugs story-better-notification-sending
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.