From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.emacs.devel Subject: Re: No commit in vc? Date: Sat, 30 Jan 2010 23:07:16 +0100 Message-ID: <877hqz9rhn.fsf@ambire.localdomain> References: <4B613BFB.2000107@swipnet.se> <87bpgev5bk.fsf@telefonica.net> <4B618AA4.1040403@swipnet.se> <87vdemtk4g.fsf@telefonica.net> <837hr23wrs.fsf@gnu.org> <87eilat62r.fsf@telefonica.net> <83eilat4g7.fsf@gnu.org> <873a1qt32z.fsf@telefonica.net> <83aavyt0bt.fsf@gnu.org> <201001290200.o0T200xh010567@godzilla.ics.uci.edu> <83y6jhs2b6.fsf@gnu.org> <201001290940.o0T9e0br025585@godzilla.ics.uci.edu> <87r5p9rxun.fsf@telefonica.net> <83vdelrx60.fsf@gnu.org> <201001291729.o0THTFam010863@godzilla.ics.uci.edu> <87ljfgdatj.fsf@telefonica.net> <83d40ssn0g.fsf@gnu.org> <873a1nk2st.fsf@ambire.localdomain> <83pr4rilv3.fsf@gnu.org> <873a1nza8y.fsf@ambire.localdomain> <83iqaji8of.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1264951940 6067 80.91.229.12 (31 Jan 2010 15:32:20 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 31 Jan 2010 15:32:20 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jan 31 16:32:18 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Nbbma-0006JT-1z for ged-emacs-devel@m.gmane.org; Sun, 31 Jan 2010 16:32:16 +0100 Original-Received: from localhost ([127.0.0.1]:39100 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NbbmZ-0003JL-H3 for ged-emacs-devel@m.gmane.org; Sun, 31 Jan 2010 10:32:15 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NbbmU-0003J8-ES for emacs-devel@gnu.org; Sun, 31 Jan 2010 10:32:10 -0500 Original-Received: from [199.232.76.173] (port=60633 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NbbmT-0003It-G3 for emacs-devel@gnu.org; Sun, 31 Jan 2010 10:32:09 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NbbmS-0002iX-Mk for emacs-devel@gnu.org; Sun, 31 Jan 2010 10:32:09 -0500 Original-Received: from host56-66-dynamic.30-79-r.retail.telecomitalia.it ([79.30.66.56]:60761 helo=ambire.localdomain) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1NbbmS-0002iN-Ah for emacs-devel@gnu.org; Sun, 31 Jan 2010 10:32:08 -0500 Original-Received: from ttn by ambire.localdomain with local (Exim 4.63) (envelope-from ) id 1NbLTI-0002HU-TO for emacs-devel@gnu.org; Sat, 30 Jan 2010 23:07:16 +0100 In-Reply-To: <83iqaji8of.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Jan 2010 23:28:48 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.91 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-Greylist: delayed 1212 seconds by postgrey-1.27 at monty-python; Sun, 31 Jan 2010 10:32:08 EST X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:120747 Archived-At: () Eli Zaretskii () Sat, 30 Jan 2010 23:28:48 +0200 > From: Thien-Thi Nguyen > Date: Sat, 30 Jan 2010 20:02:53 +0100 > > However, that is not the case universally. I can imagine a > workflow (policy) whereby a programmer needs to do several > "bzr merge" operations prior to the "bzr commit". This > programmer would view Emacs' recommendation as irrelevant at > best. This programmer knows what she is doing, and won't be averted by the recommendation. It's the same as "File FOO already exists; overwrite anyway?": The "overwrite anyway?" blurb is not the same: - It is not a recommendation. - It influences (via the user's response) Emacs' behavior. If you want it to be the same, drop "we recommend", implement "commit now?", and arrange to have that query as part of the command that produces the "pending merges" state. In the context of the proposal (as an adjunct to the status text, rather than a decision requiring user input), however, a "pending merges" blurb is sufficient: It accurately reflects the status without gratuitously presuming any particular workflow. thi