public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: marco atzeri <marco.atzeri@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] python-getdevinfo
Date: Thu, 3 Sep 2020 15:44:15 +0200	[thread overview]
Message-ID: <CAB8Xom-00TpF5oFUzW7QgyFCCV4w8aw1tpqPLPSPdv8ZuHr56w@mail.gmail.com> (raw)
In-Reply-To: <DB7PR02MB39963178BB9FCD43921642F7E72F0@DB7PR02MB3996.eurprd02.prod.outlook.com>

On Wed, Sep 2, 2020 at 10:59 PM Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>
> On 02/09/2020 19:05, Marco Atzeri via Cygwin-apps wrote:
> >
> > Hi Hamish,
> >
[cut]
> > Is already in some Linux distribution ?
> > Otherwise we need 5 votes from maintainers
>
> Hi Marco,
>
> Thanks for testing again :)
>
> Ah yes, I'm not sure how I managed to do that, they should be in the
> cygport file. I'll sort that out tomorrow and notify this list again.
>
> It's not currently in the official repositories of a Linux distro no.
> I'm essentially only packaging this for Cygwin because it's a dependency
> for DDRescue-GUI, a GUI I wrote for GNU ddrescue. I currently release
> for Linux and macOS, and there has been demand for Cygwin, hence me
> getting involved with all of this in the beginning really. I would very
> much appreciate it if I could get 5 votes, but if not I'll create some
> kind of bundle instead. I understand that this is your project and you
> may not all want my program in it :)
>
> NB: In programs that bundle cygwin.dll, are the /dev and /cygdrive
> folders visible to access devices? I'm hoping the answer is yes because
> otherwise my bundle idea probably won't work.
>
> Hamish

just to avoid misunderstandings, you have my vote, so
you need only other 3 approvals as you count as 1

Regards
Marco

  reply	other threads:[~2020-09-03 13:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17 13:33 Hamish McIntyre-Bhatty
2020-08-17 13:34 ` Hamish McIntyre-Bhatty
2020-08-19  5:53   ` Marco Atzeri
2020-08-19 11:22     ` Hamish McIntyre-Bhatty
2020-08-20  6:01       ` Marco Atzeri
2020-08-21 15:33         ` Hamish McIntyre-Bhatty
2020-08-26  9:35           ` Hamish McIntyre-Bhatty
2020-09-02 15:29             ` Hamish McIntyre-Bhatty
2020-09-02 18:05               ` Marco Atzeri
2020-09-02 20:58                 ` Hamish McIntyre-Bhatty
2020-09-03 13:44                   ` marco atzeri [this message]
2020-09-03 14:10                     ` Hamish McIntyre-Bhatty
2020-09-03 16:34                       ` Ken Brown
2020-09-03 17:13                         ` Hamish McIntyre-Bhatty
2020-09-03 17:27                           ` Hamish McIntyre-Bhatty
2020-09-03 18:50                             ` Ken Brown
2020-09-04 13:38                               ` Hamish McIntyre-Bhatty
2020-09-09 10:36                                 ` Hamish McIntyre-Bhatty
2020-09-12 22:19                                   ` Hamish McIntyre-Bhatty
2020-09-13  6:13                                     ` Achim Gratz
2020-09-13  7:39                                       ` Hamish McIntyre-Bhatty
2020-09-13 15:02                                         ` Brian Inglis
2020-09-13 16:08                                           ` Hamish McIntyre-Bhatty
2020-09-14 18:29                                             ` Hamish McIntyre-Bhatty
2020-09-13 14:57                     ` Jon Turney
2020-09-13 16:07                       ` Hamish McIntyre-Bhatty
2020-09-22 13:32                         ` Hamish McIntyre-Bhatty

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=CAB8Xom-00TpF5oFUzW7QgyFCCV4w8aw1tpqPLPSPdv8ZuHr56w@mail.gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin-apps@cygwin.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).