ftp.delorie.com/archives/browse.cgi   search  
Mail Archives: geda-user/2014/01/20/14:15:49

X-Authentication-Warning: delorie.com: mail set sender to geda-user-bounces using -f
Date: Mon, 20 Jan 2014 14:15:38 -0500
Message-Id: <201401201915.s0KJFcag016160@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: geda-user AT delorie DOT com
In-reply-to: <20140120172838.GB9705@localhost.localdomain> (message from
Vladimir Zhbanov on Mon, 20 Jan 2014 21:28:38 +0400)
Subject: Re: [geda-user] launchpad && bzr import failed
References: <20140120165851 DOT GA9705 AT localhost DOT localdomain>
<201401201705 DOT s0KH5Z2I011715 AT envy DOT delorie DOT com> <20140120172838 DOT GB9705 AT localhost DOT localdomain>
Reply-To: geda-user AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: geda-user AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

> How then launchpad knows if the fix was committed? I thought it was
> done automatically during import from git server on
> geda-project.org. Or should I manually mark that the fix for the bug
> is committed?

Dunno, that's a Peter topic.  I do know that if you include key tag lines
in the commit message, it tells the robot what to do:

Affects-bug: lp-<number>
Closes-bug: lp-<number>

But it should all be driven from our end, not from LP's end.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019