Stop using mercurial patch queues

Bug #1336440 reported by Chris Coulson
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Oxide
Fix Released
High
Chris Coulson

Bug Description

We currently have a fairly gross hack during checkout where we create a mercurial repository of the whole checkout in order to use mq to manage the patches we apply to Chromium. The reason for this is that the interface is a bit better than quilt (you don't have to do quilt add, for example), and mq is available on all distro's and all major platforms (quilt isn't).

However, using mercurial in this way has some major downsides:

- It's using a lot of disk space
- Whilst creating the repository is fast on my machine, it's taking up to an hour in canonistack

We should drop this for now and switch to quilt. A consequence of this is that it will only be possible to check the code out on linux. That kind of sucks, although I'm not sure it matters too much at the moment.

Changed in oxide:
importance: Undecided → High
status: New → Triaged
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

Let's kill this off for 1.6

Changed in oxide:
milestone: none → branch-1.6
assignee: nobody → Chris Coulson (chrisccoulson)
Changed in oxide:
milestone: branch-1.6 → branch-1.7
Changed in oxide:
milestone: branch-1.7 → none
Changed in oxide:
status: Triaged → In Progress
Revision history for this message
Chris Coulson (chrisccoulson) wrote :

It's really time we got this done. The current hack uses up 6GB of space per checkout, and is dreadfully slow

Changed in oxide:
milestone: none → branch-1.12
Changed in oxide:
status: In Progress → Fix Committed
Changed in oxide:
status: Fix Committed → Fix Released
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.