all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 29064@debbugs.gnu.org, Ricardo Wurmus <rekado@elephly.net>
Subject: [bug#29064] [PATCH] gnu: Add emacs-helm-make.
Date: Mon, 30 Oct 2017 13:02:48 -0400	[thread overview]
Message-ID: <20171030170248.GA9606@jasmine.lan> (raw)
In-Reply-To: <87po944mp6.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 928 bytes --]

On Mon, Oct 30, 2017 at 05:36:37PM +0100, Ludovic Courtès wrote:
> Hi Oleg!
> 
> Oleg Pykhalov <go.wigust@gmail.com> skribis:
> 
> > From b024832116dca28c349116c6bceae855f1ac7ea4 Mon Sep 17 00:00:00 2001
> > From: Oleg Pykhalov <go.wigust@gmail.com>
> > Date: Mon, 30 Oct 2017 09:59:46 +0300
> > Subject: [PATCH] gnu: Add emacs-helm-make.
> >
> > * gnu/packages/emacs.scm (emacs-helm-make): New variable.
> 
> LGTM!
> 
> Would you like to create an account on Savannah so we can give you
> commit access?  Please make sure to add the OpenPGP key you’ll use to
> sign commits to your Savannah account; when you’re done, please reply
> with a signed message and tell us what your account name is.

Welcome! Please also be sure to read the HACKING file in the root of the
Guix repo:

https://git.savannah.gnu.org/cgit/guix.git/tree/HACKING

It contains the guidelines related to pushing your changes.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-10-30 17:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30  7:01 [bug#29064] [PATCH] gnu: Add emacs-helm-make Oleg Pykhalov
2017-10-30 16:36 ` Ludovic Courtès
2017-10-30 17:02   ` Leo Famulari [this message]
2017-10-31  5:28     ` Oleg Pykhalov
2017-10-31  7:24       ` Ricardo Wurmus
2017-10-31 11:19         ` Oleg Pykhalov
2017-11-01 14:43       ` Ludovic Courtès

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

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

  git send-email \
    --in-reply-to=20171030170248.GA9606@jasmine.lan \
    --to=leo@famulari.name \
    --cc=29064@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=rekado@elephly.net \
    /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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.