unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Cc: 41368@debbugs.gnu.org
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 22:34:44 +0200	[thread overview]
Message-ID: <87o8qms3kr.fsf@devup.no> (raw)
In-Reply-To: <CAFkJGRd2bKX5=LULU8jc_uLEz5+qM0ZQUi8fiTM3CJxfVGkXiw@mail.gmail.com>

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

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

> On Sun, May 17, 2020, 15:56 Marius Bakke <mbakke@fastmail.com> wrote:
>
>> 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.
>>
>
> How do I do that?  This was in large part an exercise to clean up my
> development and contribution practice.

When doing 'git commit', add a one-line "title" for your change and
mention the changed files and variables in the commit message "body".

See the git log for examples.

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

  reply	other threads:[~2020-05-17 20:35 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
2020-05-17 20:30   ` Josh Marshall
2020-05-17 20:34     ` Marius Bakke [this message]
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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87o8qms3kr.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 public inbox

	https://git.savannah.gnu.org/cgit/guix.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).