[egit-dev] CQs and committing to master

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[egit-dev] CQs and committing to master

From: Alex Blewitt <alex.blewitt@xxxxxxxxx>
Date: Mon, 5 Oct 2009 14:19:14 +0100
Delivered-to: egit-dev@xxxxxxxxxxx
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:content-type:content-transfer-encoding:x-mailer :mime-version:subject:date; b=XSe34eTV5mduvklOPNX4sXMm94JIh6QYQHaf946nPicorXKNOGAMapdtVUE2V/VT3S +XDCZvAGLzBRT21yFcnIQiBYV23CQfP5iPSyeFd75FRKevlud8EtolpQThBpJ8rnNfvf GsfOhN+XHT26eiGrDZ/F2jf8+aeYXiBhhT4+Y=
List-archive: <https://dev.eclipse.org/mailman/private/egit-dev>
List-help: <mailto:egit-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/egit-dev>, <mailto:egit-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/listinfo/egit-dev>, <mailto:egit-dev-request@eclipse.org?subject=unsubscribe>

It seems the CQ is causing a backlogette at the moment. How doesgerrit handle branching; could we have a branch for items needing a CQand then let other items overtake later and get the CQ stuff mergedback in?


Alex

Sent from my (new) iPhone

Follow-Ups:
- Re: [egit-dev] CQs and committing to master
  - From: Shawn O. Pearce
- Re: [egit-dev] CQs and committing to master
  - From: Chris Aniszczyk

Prev by Date: Re: [egit-dev] NLS and JGit
Next by Date: Re: [egit-dev] CQs and committing to master
Previous by thread: [egit-dev] JUnit test cleanups
Next by thread: Re: [egit-dev] CQs and committing to master
Index(es):
- Date
- Thread

Breadcrumbs