From: Marco Atzeri <marco.atzeri@gmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Ejecting a USB drive using Cygwin (sync)?
Date: Thu, 25 Jan 2018 12:45:00 -0000 [thread overview]
Message-ID: <d1dfcd41-39d3-9ead-a91d-f9ec6e586a15@gmail.com> (raw)
In-Reply-To: <5a67c70d.89349d0a.83b53.40f2@mx.google.com>
On 24/01/2018 07:36, Steven Penny wrote:
> On Tue, 23 Jan 2018 14:13:24, Brian Inglis wrote:
>> I found the following utility works well without elevation - Windows
>> code from
>> http://www.leapsecond.com/tools/eject.{c,exe}:
the original code location is reported
>>
>> // eject -- Allow safe removal of USB thumb drive.
>> // - Command line tool to flush/dismount/eject USB drive.
>> // - Simpler than mouse clicking through taskbar "Safely Remove
>> Hardware" icon.
>> // - Usable in batch file scripts.
>> // 02-Nov-2012 Tom Van Baak (tvb) www.LeapSecond.com/tools
>> ...
The proper copyright is reported, the "..."
are clearly showing an extract posted in line.
>> // Per MSDN, follow procedure for safe removal of USB drive.
>
> No, this is not the code from that site. The code is similar, but I see
> you have
> at least removed some empty lines. If you are going to do so, you need to
> clearly present said changes to the community - something like "adapted
> from
> http://..." or "modified from http://...", etc.
>
> Software copyright - even open source license is serious, and you should
> give it
> due respect.
>
he was not providing a full functional code, not claiming ownership,
just highlighting the key calls.
It seems to me that you are barking to the wrong tree.
Marco
--
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
prev parent reply other threads:[~2018-01-25 12:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-23 11:14 Ronald Fischer
2018-01-23 15:41 ` Nem W Schlecht
2018-01-23 18:50 ` Andrey Repin
2018-01-23 21:13 ` Brian Inglis
2018-01-23 23:36 ` Steven Penny
2018-01-25 3:02 ` Brian Inglis
2018-01-25 9:58 ` David Allsopp
2018-01-25 20:37 ` Brian Inglis
2018-01-25 21:43 ` Doug Henderson
2018-01-26 1:31 ` Brian Inglis
2018-01-25 12:45 ` Marco Atzeri [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=d1dfcd41-39d3-9ead-a91d-f9ec6e586a15@gmail.com \
--to=marco.atzeri@gmail.com \
--cc=cygwin@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).