public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Arun Prakash Jana <engineerarun@gmail.com>
To: Marco Atzeri <marco.atzeri@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: Package request: nnn file manager
Date: Mon, 06 Jan 2020 15:37:00 -0000	[thread overview]
Message-ID: <CANLaLhZQ3ec4hhRoJpEQci6h+X=VVPoznUH00EeSqj9_MYA6Lg@mail.gmail.com> (raw)
In-Reply-To: <08594716-ac94-ec46-9272-fb711dd1d5d5@gmail.com>

> generally because they're maintaining packages they use themselves.

I understand. There were some user requests due to which we enabled
Cygwin support. Perhaps we will request the users. Thanks for the
relevant links.

> For what it's worth, I took a quick look at your Cygwin installation instructions.

This is automated now if with the respective program option. I have
updated the document. Thanks for letting me know!

Regards,

Arun

On Mon, Jan 6, 2020 at 8:10 PM Marco Atzeri <marco.atzeri@gmail.com> wrote:
>
> Am 06.01.2020 um 10:44 schrieb Arun Prakash Jana:
> > Hi Marco,
> >
> > I noticed your response now. Somehow I didn't receive a mail when you responded.
>
> this is a mailing list.
> If you are not subscribed you do not see replies.
> Adding you in CC
>
> > I would have loved to contribute but I do not have access to any
> > Windows system for personal usage. So I requested in this mailing list
> > if someone can pick it up.
>
> Maybe.
>
> > Regards,
> >
> > Arun
>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2020-01-06 15:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-05 20:22 Arun Prakash Jana
2020-01-05 21:21 ` Marco Atzeri
2020-01-06  9:45 ` Arun Prakash Jana
2020-01-06 14:40   ` Marco Atzeri
2020-01-06 15:37     ` Arun Prakash Jana [this message]
2020-01-06 14:44   ` Adam Dinwoodie
2020-01-06 17:39     ` Brian Inglis

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='CANLaLhZQ3ec4hhRoJpEQci6h+X=VVPoznUH00EeSqj9_MYA6Lg@mail.gmail.com' \
    --to=engineerarun@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=marco.atzeri@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).