X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=rYJu29mmy7xlR1aeLAEhbUUirU2cpKQqS8JixDb7C8MP+PVVfyIbG jZ4is5PQokgmEFlC6zEINY/6cQxosbeKU0EV5cc2pzqRyoNPsalw5PPWiUHJhkDV uolW/q1UG/YZoNCzkdFPA3LKxbzFdQF9LVEfjZxbkRzbPL4JS9fUz4= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=ZwPINXT4cFrbmxrPm/YofFW/mqk=; b=LZTeo9L6Q7Xfm134F5cFojLA7rsq 4PRgYteQ7tLppBt9CBXYtHHHV9r45KK+NG8VokhDka2/A5aBSscMnFz6jDU5CyD+ 525sxOqQ1sZfTl3nrVeiw4vqYvFDdgdwnYHRNhJk7KKKxoun5JL7ugnSgRZpwNKV 9KYvGBsQr/49XtY= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00,TW_YG autolearn=ham version=3.3.1 Date: Tue, 21 May 2013 18:05:10 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Patch for shutdown Message-ID: <20130521160510.GO2406@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20130521094222 DOT GF2406 AT calimero DOT vinschen DOT de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) On May 21 17:20, Frank Fesevur wrote: > 2013/5/21 Corinna Vinschen: > > I'm a bit reluctant as of the backward compatibility breakage. What > > if somebody uses shutdown in a script? You know, starting a backup > > in the evening and the last action of the script is to hibernate the > > machine or something like that... > > That's why I sent my email in March in the first place. But I really > think having -h for halt is better for a POSIX/Linux-like shutdown. > And "shutdown -h now" will now halt the machine instead of hibernate. > Although I understand they definitely are not the same, it won't leave > the machine turned on. It will be in a "form of off". > > A proper announcement is required. The backward compatibility breakage > was the reason I thought about 2.x vs 1.x. > > > Say, do you want to take over shutdown > > maintainership? It's an easy enough package to start with, it > > builds fine on 32 and 64 bit, and you get the cygport configuration > > "for free". What do you say? > > Anything "for free" must be good ;-) > > I see the cygport file is in src archive. It has been very long since > I have played with cygport. > > And I have not looked at cygwin64, although I use Win7-64. I had no > real need for cygwin64 so far, so I wanted to wait for it to be > officially released. I just ran the setup64.exe found at a nearby > mirror, installed cygport and gcc/g++ and shutdown compiles under 32 > and 64 bit. > > So back to the question... why not take over? I will read > http://cygwin.com/setup.html thoroughly, create the new packages and > send the ITA any time soon. Cool, thanks! > You keep the sources in CVS right now. But when I take over, I assume > it is ok I put them at my github. Uhm... I would prefer if we had the cygwin-specific tools in a single repository, if it's not asked too much. I'm sure we could add git access as well, if it's not already available. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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