From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Campbell Subject: Re: [OSSTEST PATCH 11/27] ap-push: Use refs/heads/ for destinations Date: Wed, 16 Sep 2015 14:57:48 +0100 Message-ID: <1442411868.18856.78.camel@citrix.com> References: <1442410530-9665-1-git-send-email-ian.jackson@eu.citrix.com> <1442410530-9665-12-git-send-email-ian.jackson@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1ZcDDd-0000BK-Rv for xen-devel@lists.xenproject.org; Wed, 16 Sep 2015 13:57:53 +0000 In-Reply-To: <1442410530-9665-12-git-send-email-ian.jackson@eu.citrix.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Jackson , xen-devel@lists.xenproject.org List-Id: xen-devel@lists.xenproject.org On Wed, 2015-09-16 at 14:35 +0100, Ian Jackson wrote: > When the destination is a branch, specify refs/heads/ explicitly. > This makes ap-push work even if the ref does not yet exist on the > destination. > > There is no functional change for an existing installation pushing to > an existing branch. But for a hypothetical new installation, this > would be necessary. > > And, more relevantly, when new "branches" are invented, the use of an > existing ap-push case as a template will generate a new case which > creates the branch as is necessary. > > I leave the more complex osstest case alone. It's not clear to me > whether the destination ref not existing is an installation problem of > such severity that indeed ap-push should fail. > > Signed-off-by: Ian Jackson Acked-by: Ian Campbell