From: Ruthard Baudach <ruthard.baudach@web.de>
To: Gaute Hope <eg@gaute.vetsj.com>
Cc: supmua <supmua@googlegroups.com>
Subject: Re: [sup] [PATCH] added command line argument to sup invocation: "sup email-address" invokes sup in command line
Date: Sat, 15 Nov 2014 10:57:59 +0100 [thread overview]
Message-ID: <1416045204-sup-6555@ruthard-lappi> (raw)
In-Reply-To: <1415959463-astroid-0-4xu4dq0h0g-7223@strange>
[-- Attachment #1.1: Type: text/plain, Size: 789 bytes --]
>== Auszüge aus der Nachricht von Gaute Hope vom 2014-11-14 11:13:
> got a few comments below [btw: it is better to send a completely new
> patch with your changes squashed together than to send incremental
> changes to the first patch].
I really found no way to do this, as far as I understood it, it's
intentional that format-patch preserves all commits by means of
incremental patches. I just re-cloned the repository.
The patch attached will add addresses provided by --compose and as
arguments. No checks on validity of the provided addresses are done, as
the --compose option did not check the validity up to now and users
are able to view and correct typing mistakes in compose mode.
Regards, Ruthard
--
Please encrypt and sign emails.
My PGP-Id: AC5AC6C2
[-- Attachment #1.2: 0001-email-command-argument-support.patch --]
[-- Type: application/x-msdos-program, Size: 1694 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-11-16 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 18:37 Ruthard Baudach
2014-11-14 10:13 ` [sup] " Gaute Hope
2014-11-14 21:48 ` Ruthard Baudach
2014-11-16 11:17 ` Gaute Hope
2014-11-15 9:57 ` Ruthard Baudach [this message]
2014-11-16 11:25 ` Gaute Hope
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=1416045204-sup-6555@ruthard-lappi \
--to=ruthard.baudach@web.de \
--cc=eg@gaute.vetsj.com \
--cc=supmua@googlegroups.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox