> export INFOPATH="$HOME/guix/doc${INFOPATH:+:}$INFOPATH"
>
> where $HOME/guix is my local checkout of Guix's Git repository. This
> ensures that the manual I read using Emacs and the Info reader matches
> the Guix code I have checked out (after I've built it, of course). Do
> you think it woul
Leo Famulari writes:
> On Sat, Apr 29, 2017 at 07:48:15PM -0700, Chris Marusich wrote:
>> In the current master branch, this has been changed to "guix-patches".
>> Perhaps somebody needs to update the website, too? The website is
>> only updated periodically, so sometimes it is out of date.
>
>
On Sat, Apr 29, 2017 at 07:48:15PM -0700, Chris Marusich wrote:
> In the current master branch, this has been changed to "guix-patches".
> Perhaps somebody needs to update the website, too? The website is
> only updated periodically, so sometimes it is out of date.
The web-based manual correspond
Hi Chris,
On Sat, 29 Apr 2017 19:48:15 -0700
Chris Marusich wrote:
>
> Yes, this wording is unclear. It could be interpreted as an invitation
> to send bug reports and patches to guix-devel@, which is not quite
> right.
>
> On related note, I see there is a section on submitting patches ((guix
Petter writes:
> Hi Guix,
>
> I quite recently realized I sent a couple of patches to guix-devel, whereas
> they should now go to guix-patches. I use the online manual and the current
> state is that there's a couple of references to guix-devel for submitting
> patches.
>
> https://www.gnu.org/so
Hi Petter!
I think all of the different mailing lists used by Guix and their intended use
should be mentioned and or corrected in the manual (sending patches , reporting
bugs, discussing ideas or requesting help, etc.)
Hi Guix,
I quite recently realized I sent a couple of patches to guix-devel, whereas
they should now go to guix-patches. I use the online manual and the current
state is that there's a couple of references to guix-devel for submitting
patches.
https://www.gnu.org/software/guix/manual/html_node/Su
