git: "bzr send" should not set revision-id in commit when roundtripping

Bug #579272 reported by Jelmer Vernooij
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Git Plugin
Triaged
Medium
Unassigned
Breezy
Fix Released
Medium
Jelmer Vernooij

Bug Description

  affects bzr-git
  status triaged
  importance high

"bzr send" currently looks for the shas of Bazaar revisions in the local
git object store, and those are created with roundtripping support
enabled. It should instead use the lossy version or at least avoid
including the revision id, so when the revision (perhaps modified) is
applied by upstream we don't end up breaking referential integrity.

Jelmer Vernooij (jelmer)
summary: - "bzr send" should not set revision-id in commit
+ "bzr send" should not set revision-id in commit when roundtripping
Changed in bzr-git:
importance: High → Medium
Jelmer Vernooij (jelmer)
Changed in brz-git:
status: New → Triaged
importance: Undecided → Medium
assignee: nobody → Jelmer Vernooij (jelmer)
status: Triaged → Fix Released
Jelmer Vernooij (jelmer)
Changed in brz-git:
milestone: none → integration
Jelmer Vernooij (jelmer)
affects: brz-git → brz
Changed in brz:
milestone: integration → none
milestone: none → 3.0.0
summary: - "bzr send" should not set revision-id in commit when roundtripping
+ git: "bzr send" should not set revision-id in commit when roundtripping
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.