all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: WIP Guix Cookbook
Date: Sun, 15 Sep 2019 23:19:09 +0200	[thread overview]
Message-ID: <3C59475C-0201-4033-A75D-98308F839DD4@lepiller.eu> (raw)
In-Reply-To: <878sqpr5m4.fsf@elephly.net>

Le 15 septembre 2019 16:33:55 GMT+02:00, Ricardo Wurmus <rekado@elephly.net> a écrit :
>
>Hi Julien,
>
>>>Thanks for the information.  Would you like to make these changes? 
>I’m
>>>not sure how to do this.
>[…]
>
>> Sure, but I'm not sure what workflow is when working on a wip-
>> branch. Can I simply amend your patch and push-force it to the
>branch?
>
>Thanks.  You could just push a new commit that implements the changes.
>Before we merge the branch I can squash the commits.
>
>--
>Ricardo

I think I managed to do what I wanted: making sure make dist works. You will need to run make doc-po-update before, and putting it in dist-hook doesn't change anything. We'll have to run that for the TP so translators can start working on the cookbook.

I disabled all traslations for the cookbook since there is none for now. Adding a new language for the cookbook is the same process as for tge manual.

      reply	other threads:[~2019-09-15 21:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08 13:07 WIP Guix Cookbook Ricardo Wurmus
2019-09-08 18:57 ` Pierre Neidhardt
2019-09-09  7:10   ` Ricardo Wurmus
2019-09-08 19:01 ` L p R n d n
2019-09-11 20:02 ` Ludovic Courtès
2019-09-14 22:33   ` Ricardo Wurmus
2019-09-15  7:43     ` Julien Lepiller
2019-09-15 12:01       ` Ricardo Wurmus
2019-09-15 14:25         ` Julien Lepiller
2019-09-15 14:33           ` Ricardo Wurmus
2019-09-15 21:19             ` Julien Lepiller [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

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

  git send-email \
    --in-reply-to=3C59475C-0201-4033-A75D-98308F839DD4@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=guix-devel@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.