From: Thomas Wolff <towo@towo.net>
To: Vince Rice <vrice@solidrocksystems.com>
Cc: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mintty 2.9.9
Date: Thu, 28 Mar 2019 21:34:00 -0000 [thread overview]
Message-ID: <e95db126-2d00-338e-8895-6fddc5eec94b@towo.net> (raw)
In-Reply-To: <8E2399DD-C9E8-4973-A9F2-204CDA4ABCF3@solidrocksystems.com>
Am 28.03.2019 um 19:38 schrieb Vince Rice:
>> On Mar 28, 2019, at 1:33 PM, Thomas Wolff wrote:
>>
>> Am 28.03.2019 um 19:16 schrieb Vince Rice:
>>>> On Mar 28, 2019, at 1:09 PM, Thomas Wolff wrote:
>>>>
>>>>> A potential solution is, add another user to your system named cygwin.
>>>>> When you build you packages use the cygwin user. The debug information
>>>>> will reference your cygwin user, and not your real user account.
>>>> Thanks for the suggestion, but there are other solutions meanwhile. Also, you would have
>>>> to remember to switch user everytime, which may take a while, and it's not even possible
>>>> to create user accounts on everybody's machine.
>>> You're the only one that needs to remember, and it's only your machine that would need the
>>> the user account. Other people building the package don't have the same ⦠requirements â¦
>>> you do. They're not distributing what they build. They would just use the cygport and be done
>>> with it.
>>>
>>> (Not selling the solution as I have no opinion on it, just pointing out that neither of those
>>> objections are really a problem.)
>> What I wanted to point out with my last objection is that some people may not be able to create an account as they like, in an enterprise environment.
> And what I was pointing out is that nobody but you needs to. This whole thread is about trying
> to solve *your* problem, not someone else's. As I said, if I built mintty, I would just use cygport
> and be done with it. I don't care about user information, because I'm not distributing the package.
It's a bit strange that you're telling my that *you* don't care about
*my* information.
I'm trying to raise some awareness about privacy on this occasion (which
is quite a topic nowadays) and if you don't care, you don't need to comment.
--
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
next prev parent reply other threads:[~2019-03-28 21:34 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-16 9:35 Thomas Wolff
2019-03-16 14:01 ` Achim Gratz
2019-03-24 14:51 ` Steven Penny
2019-03-24 15:57 ` Thomas Wolff
2019-03-24 16:24 ` Brian Inglis
2019-03-24 18:19 ` Corinna Vinschen
2019-03-24 23:36 ` Thomas Wolff
2019-03-25 8:31 ` Corinna Vinschen
2019-03-25 18:12 ` Achim Gratz
2019-03-27 20:02 ` Thomas Wolff
2019-03-27 20:36 ` Achim Gratz
2019-03-27 21:01 ` Jeffrey Walton
2019-03-27 22:52 ` Steven Penny
2019-03-27 23:09 ` Yaakov Selkowitz
2019-03-28 1:12 ` Steven Penny
2019-03-28 2:35 ` Yaakov Selkowitz
2019-03-28 2:44 ` Brian Inglis
2019-03-28 3:42 ` Steven Penny
2019-03-28 7:34 ` Thomas Wolff
2019-03-28 11:36 ` Steven Penny
2019-03-28 15:09 ` Brian Inglis
2019-03-28 18:22 ` Dependancy Hell (was Re: [ANNOUNCEMENT] Updated: mintty 2.9.9) Chris Wagner
2019-03-28 17:37 ` [ANNOUNCEMENT] Updated: mintty 2.9.9 Achim Gratz
2019-03-27 22:59 ` Yaakov Selkowitz
2019-03-28 7:15 ` Björn Stabel
2019-03-28 17:40 ` Achim Gratz
2019-03-28 18:08 ` Thomas Wolff
2019-03-28 18:21 ` Achim Gratz
2019-03-28 18:32 ` Thomas Wolff
2019-03-28 19:47 ` Achim Gratz
2019-03-28 21:38 ` Thomas Wolff
2019-03-28 8:43 ` Thomas Wolff
2019-03-28 9:36 ` Corinna Vinschen
2019-03-28 14:02 ` Jeffrey Walton
2019-03-28 18:10 ` Thomas Wolff
2019-03-28 18:16 ` Vince Rice
2019-03-28 18:33 ` Thomas Wolff
2019-03-28 18:43 ` Vince Rice
2019-03-28 21:34 ` Thomas Wolff [this message]
2019-03-28 22:28 ` Steven Penny
2019-03-24 21:05 ` Andrey Repin
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=e95db126-2d00-338e-8895-6fddc5eec94b@towo.net \
--to=towo@towo.net \
--cc=cygwin@cygwin.com \
--cc=vrice@solidrocksystems.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).