public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Cc: ricardo.couto@gmail.com
Subject: Re: email -attach
Date: Mon, 4 Jul 2022 15:18:37 -0600	[thread overview]
Message-ID: <77c05da4-8187-eda7-2b60-e633a84d96e4@SystematicSw.ab.ca> (raw)
In-Reply-To: <8b5bdf9a-5f90-cccf-0440-c2fff1bd04b6@gmail.com>

On 2022-07-04 14:43, Marco Atzeri wrote:
> On 04.07.2022 21:03, ricardo.couto@gmail.com wrote:
>> I know -attach  file1 -attach file2 -attach file 3 works fine.
>> I just sugest you implemente a code with -attach "file1, file2, file3".

That stops anyone attaching files with names containing ","!

> It seems you have not clear the difference between
> upstream package code and distributions like Cygwin.
> In the case of "email" the upstream code is developed at
> https://github.com/deanproxy/eMail
> the Cygwin package maintainer takes upstream releases
> and build the Cygwin binary packages.
> New feature are managed upstream, not by the Cygwin packager.

For open upstream sources, suggestions are "two|ten a penny"|"dime a 
dozen"|"não são de grande valia"!
They typically expect you to make the necessary implementation code 
changes on a fork of the project on Github, and send them a Pull Request 
(PR, or a patch file) referencing the commit, including changes to 
documentation and release notes.

They and we are volunteers, so have to choose where we spend our time.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

      reply	other threads:[~2022-07-04 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 20:19 ricardo.couto
2022-07-01 15:33 ` Brian Inglis
2022-07-01 17:00   ` RES: " ricardo.couto
2022-07-02  0:14     ` Andrey Repin
2022-07-04 13:23       ` RES: " ricardo.couto
2022-07-04 18:51         ` Brian Inglis
2022-07-04 19:03           ` RES: " ricardo.couto
2022-07-04 20:43             ` Marco Atzeri
2022-07-04 21:18               ` Brian Inglis [this message]

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=77c05da4-8187-eda7-2b60-e633a84d96e4@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.com \
    --cc=ricardo.couto@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.
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).