unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Third <alan@idiocy.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: master 89286b1 1/2: Add GNUstep build to Gitlab CI/CD
Date: Sat, 29 Aug 2020 17:34:49 +0200 (CEST)	[thread overview]
Message-ID: <20200829153447.GA65922@breton.holly.idiocy.org> (raw)
In-Reply-To: <87sgc57jx4.fsf@gmx.de>

On Sat, Aug 29, 2020 at 01:47:51PM +0200, Michael Albinus wrote:
> alan@idiocy.org (Alan Third) writes:
> 
> Hi Alan,
> 
> >     Add GNUstep build to Gitlab CI/CD
> >
> >     * .gitlab-ci.yml (test-gnustep): New test target.
> >
> > +test-gnustep:
> > +  stage: test
> > +  # This tests the GNUstep build process
> > +  only:
> > +    changes:
> > +      - .gitlab-ci.yml
> > +      - configure.ac
> > +      - src/nsfns.m
> > +      - src/nsfont.m
> > +      - src/nsgui.h
> > +      - src/nsimage.m
> > +      - src/nsmenu.m
> > +      - src/nsselect.m
> > +      - src/nsterm.h
> > +      - src/nsterm.m
> > +      - src/nsxwidget.h
> > +      - src/nsxwidget.m
> > +      - src/macfont.h
> > +      - src/macfont.m
> 
> There are also lisp/term/ns-win.el and nextstep/* files. Should they be
> counted here as well?

I had skipped ns-win.el as it's not really important to the build but
on reflection it might still break it, so it probably should be added.
I hadn't thought of the nextstep/* files, and they should be.

I've pushed an updated list of files. Thanks!
-- 
Alan Third



      reply	other threads:[~2020-08-29 15:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200828184728.15833.56344@vcs0.savannah.gnu.org>
     [not found] ` <20200828184730.789C120A10@vcs0.savannah.gnu.org>
2020-08-29 11:47   ` master 89286b1 1/2: Add GNUstep build to Gitlab CI/CD Michael Albinus
2020-08-29 15:34     ` Alan Third [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200829153447.GA65922@breton.holly.idiocy.org \
    --to=alan@idiocy.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).