From: Danny Milosavljevic <dannym@scratchpost.org>
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Simplify dtc package definition.
Date: Thu, 8 Sep 2016 19:55:39 +0200 [thread overview]
Message-ID: <20160908195539.4d47016d@scratchpost.org> (raw)
In-Reply-To: <CAL1_immMJ5E-7Kxggr=vXGg1H0Nrmq60bQYR8h5=Wh0SYPYY4Q@mail.gmail.com>
Hi David,
On Thu, 8 Sep 2016 17:09:12 +0200
David Craven <david@craven.ch> wrote:
> Why aren't you using git format-patch? :)
>
> git format-patch -1
> git send-email *.patch --to guix-devel@gnu.org
>
> is what I do...
That's exactly what I do too - the exact same commands. I don't know what magical options other people use but that's how it always comes out for me. I usually manually copy&paste the subject back down into the body - but this time I forgot. Regardless, that was a bona fide git format-patch AND git send-email E-Mail.
On the other hand, Linux people also told me about my git format-patch settings being "wrong" - and indeed they are different than the ones I use to submit to Guix.
What are the settings you use / we should use?
Mine are:
$ git config --global -l |grep ^format
format.subjectprefix=FIXME
format.numbered=auto
format.signoff=false
format.coverletter=auto
format.signature=
format.attach=
And the git-format-patch executable is built from GuixSD svn master hydra from a few days ago...
next prev parent reply other threads:[~2016-09-08 17:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-07 7:46 [PATCH] gnu: Simplify dtc package definition Danny Milosavljevic
2016-09-07 8:15 ` David Craven
2016-09-07 9:01 ` Danny Milosavljevic
2016-09-08 15:09 ` David Craven
2016-09-08 17:55 ` Danny Milosavljevic [this message]
2016-09-08 18:45 ` David Craven
2016-09-08 19:32 ` Danny Milosavljevic
2016-09-08 20:16 ` David Craven
2016-09-10 18:19 ` Leo Famulari
2016-09-10 18:22 ` David Craven
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=20160908195539.4d47016d@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=david@craven.ch \
--cc=guix-devel@gnu.org \
/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.