gcommit should load default comments (from "bzr uncommit" and UI button "cancel but retain")

Bug #180109 reported by Chad Miller
2
Affects Status Importance Assigned to Milestone
Bazaar GTK+ Frontends
Triaged
Wishlist
Unassigned

Bug Description

Using bzr-gtk's "gcommit" verb, there may be several fields to fill if one has per-file commit messages on. These should be loaded from disc if there were comments previously stored.

There should be two ways that default comments may be stored:
 * "bzr uncommit",
 * in the gcommit UI, a button "Cancel and retain comments".

Tags: gcommit
Revision history for this message
Daniel Schierbeck (dasch) wrote :

We need to decide on how to store the messages. The current option system probably won't suffice.

Changed in bzr:
status: New → Confirmed
Revision history for this message
Szilveszter Farkas (phanatic) wrote :

This bug is related to bzr-gtk (not Bazaar), so I mark it as Invalid for Bazaar.

Changed in bzr:
status: Confirmed → Invalid
Changed in bzr-gtk:
status: New → Confirmed
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Maybe we can store the revision metadata in serialized form on disk somewhere? somewhere in .bzr/checkout/ perhaps?

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

this seems related to bzr as well, since bzr uncommit would need to store this info (and ideally we'd share the same store as qbzr)

Changed in bzr-gtk:
importance: Undecided → Wishlist
status: Confirmed → Triaged
Changed in bzr:
importance: Undecided → Wishlist
status: Invalid → Triaged
tags: added: gcommit
Martin Pool (mbp)
Changed in bzr:
status: Triaged → Confirmed
Jelmer Vernooij (jelmer)
no longer affects: bzr
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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