unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Polyakov <polyakov@liltechdude.xyz>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 46378@debbugs.gnu.org
Subject: [bug#46378] [PATCH] gnu: Add instead.
Date: Mon, 08 Feb 2021 12:15:03 -0500	[thread overview]
Message-ID: <87v9b2cwh4.fsf@liltechdude.xyz> (raw)
In-Reply-To: <6398b29a976e3e804e224268fd58afd26326b35b.camel@student.tugraz.at>

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


Leo Prikler writes:

> the patch now applies with "git apply", but not "git am", which 
> makes
> it difficult to sign off.  I can however rewrite the commit on your
> behalf if that is what you want.

No, my goal is to send as good patch as possible without any stuff 
like
rewriting patch by maintainer. My first patch was submitting with
copy-pasting patch from output of magit `W c c` to message-buffer, but
format=flowed (as this artcle https://useplaintext.email/ urges) in 
m4ue
wrap some lines and therefore inline patch is brocken.

Second sended by `git send-email --to="46378@debbugs.gnu.org" HEAD^`.

May be I should turn off format=flowed option? Or send patch as 
attached
file? I dunno what way is produce minimal effort by your side, so 
please
tell me.

Sorry, I literally have no expirience with email driven changes
submitting before.

--
魔法少女リルテチヅデですよ。

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

  reply	other threads:[~2021-02-08 22:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-08  7:23 [bug#46378] [PATCH] gnu: Add instead Dmitry Polyakov
2021-02-08 12:46 ` Leo Prikler
2021-02-08 13:04   ` Dmitry Polyakov
2021-02-08 14:11 ` polyakov
2021-02-08 15:46   ` Leo Prikler
2021-02-08 17:15     ` Dmitry Polyakov [this message]
2021-02-08 17:43       ` Leo Prikler
2021-08-04 12:29 ` polyakov
2021-08-04 13:50   ` bug#46378: " Leo Prikler

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=87v9b2cwh4.fsf@liltechdude.xyz \
    --to=polyakov@liltechdude.xyz \
    --cc=46378@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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).