all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: joshua.r.marshall.1991@gmail.com, 41368@debbugs.gnu.org
Cc: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Subject: [bug#41368] [PATCH] Moved gettext to use git to better conform to better bootstrapping, better integration with Software Heritage, and what looks like emerging best practices for package sources.
Date: Sun, 17 May 2020 21:56:17 +0200	[thread overview]
Message-ID: <87r1vis5cu.fsf@devup.no> (raw)
In-Reply-To: <20200517194400.349638-1-joshua.r.marshall.1991@gmail.com>

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

joshua.r.marshall.1991@gmail.com writes:

> From: Josh Marshall <joshua.r.marshall.1991@gmail.com>

Please add commit messages following the GNU ChangeLog style to your
patches.

I'm surprised that this does not require adding Autoconf etc as
native-inputs, do you know why that is?

Also, won't this cause a circular dependency on 'git-minimal'?  If it
works for you I guess we got lucky in this case.

AIUI the lack of tarball integration in Software Heritage is temporary,
i.e. it will eventually be sorted, and of course back-dated.  So I don't
think we need to move everything to git while we wait for that.

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

  reply	other threads:[~2020-05-17 19:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-17 19:44 [bug#41368] [PATCH] Moved gettext to use git to better conform to better bootstrapping, better integration with Software Heritage, and what looks like emerging best practices for package sources joshua.r.marshall.1991
2020-05-17 19:56 ` Marius Bakke [this message]
2020-05-17 20:30   ` Josh Marshall
2020-05-17 20:34     ` Marius Bakke
2020-05-18 18:04     ` Leo Famulari
2020-10-28 18:26     ` zimoun

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=87r1vis5cu.fsf@devup.no \
    --to=mbakke@fastmail.com \
    --cc=41368@debbugs.gnu.org \
    --cc=joshua.r.marshall.1991@gmail.com \
    /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.