From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kaushal Modi Subject: Re: Probably broke the Worg build? Date: Sat, 06 Jan 2018 02:05:48 +0000 Message-ID: References: <87d12yojyn.fsf@bzg.fr> <87zi61xz5e.fsf@gnu.org> <87zi5t8pfn.fsf@Rainer.invalid> <87a7xth30x.fsf@nicolasgoaziou.fr> <87373jhhu7.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="94eb2c146f4a9f5e0a0562120187" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38371) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eXds4-0002te-IA for emacs-orgmode@gnu.org; Fri, 05 Jan 2018 21:06:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eXds3-0002yH-GP for emacs-orgmode@gnu.org; Fri, 05 Jan 2018 21:06:04 -0500 In-Reply-To: <87373jhhu7.fsf@gnu.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Bastien Cc: emacs-orgmode@gnu.org, Nicolas Goaziou --94eb2c146f4a9f5e0a0562120187 Content-Type: text/plain; charset="UTF-8" On Fri, Jan 5, 2018 at 8:55 PM Bastien wrote: > Hi Kaushal, > > I republished Worg manually and things went fine. But I had to kill > a stuck process before running this new one. I'll try to understand > what happened when I have more time at end. > Thanks! I just pushed one more commit ( https://code.orgmode.org/bzg/worg/commit/4feac9160363279653a3d19cf68619e6a9c02fee ).. let's see if that freezes up the build again. I am using https to push the commits. That shouldn't matter, right? Because the commits do end up showing fine on code.orgmode.org. Thanks for the fixes! > My pleasure. -- Kaushal Modi --94eb2c146f4a9f5e0a0562120187 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Jan 5,= 2018 at 8:55 PM Bastien <bzg@gnu.org= > wrote:
Hi Kaushal,

I republished Worg manually and things went fine.=C2=A0 But I had to kill a stuck process before running this new one.=C2=A0 I'll try to understa= nd
what happened when I have more time at end.

=
Thanks! I just pushed one more commit ( https://cod= e.orgmode.org/bzg/worg/commit/4feac9160363279653a3d19cf68619e6a9c02fee = ).. let's see if that freezes up the build again. I am using https to p= ush the commits. That shouldn't matter, right? Because the commits do e= nd up showing fine on code.orgmode.org<= /a>.
Thanks for the fixes!



--

Kaushal Mo= di

--94eb2c146f4a9f5e0a0562120187--