From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ivan Shmakov Newsgroups: gmane.emacs.devel Subject: Re: VC mode and git Date: Sat, 28 Mar 2015 09:05:26 +0000 Message-ID: <87a8yxv6eh.fsf@violet.siamics.net> References: <86egoeusg2.fsf@example.com> <87384qzxqy.fsf@igel.home> <83bnjen71r.fsf@gnu.org> <83twx6a7wm.fsf@gnu.org> <83sicq1cvt.fsf@gnu.org> <83k2y21b9n.fsf@gnu.org> <87d23uchvd.fsf@wanadoo.es> <83a8yx1tgw.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1427533568 22885 80.91.229.3 (28 Mar 2015 09:06:08 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 28 Mar 2015 09:06:08 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Mar 28 10:06:02 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Ybmgn-00053l-I1 for ged-emacs-devel@m.gmane.org; Sat, 28 Mar 2015 10:05:57 +0100 Original-Received: from localhost ([::1]:53208 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ybmgk-0006gx-RD for ged-emacs-devel@m.gmane.org; Sat, 28 Mar 2015 05:05:56 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38949) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ybmgh-0006go-Lb for emacs-devel@gnu.org; Sat, 28 Mar 2015 05:05:53 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Ybmgg-0002zS-1o for emacs-devel@gnu.org; Sat, 28 Mar 2015 05:05:51 -0400 Original-Received: from fely.am-1.org ([2a01:4f8:d15:1b86::2]:44676) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Ybmgf-0002ni-OL for emacs-devel@gnu.org; Sat, 28 Mar 2015 05:05:49 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=siamics.net; s=a2013295; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:In-Reply-To:Date:Sender:References:Subject:To:From; bh=kDeZLw2gHBr1m4UUXUVUnWFttKli1morYB8s0LIhw+4=; b=jjsumVJlfgh140tAw+DSnzHxhFbDxIPznhxo5Yz1gkWj8j9ws6sb7g0nBCib2mpbeKMsk6IkPE2yY+OfySUl/ffAFBmIOIMqxR2TcIVER6x/Xwz2vRogIyIEuKa8Tjy0LQuAfNTCXVw5k6fjGzyvw/6+qSJdqIwgn5q+ooZrxQc=; Original-Received: from [2a02:2560:6d4:26ca::1:1d] (helo=violet.siamics.net) by fely.am-1.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1YbmgS-0004p8-4B for emacs-devel@gnu.org; Sat, 28 Mar 2015 09:05:36 +0000 Original-Received: from localhost ([::1] helo=violet.siamics.net) by violet.siamics.net with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1YbmgK-0000sG-Uu for emacs-devel@gnu.org; Sat, 28 Mar 2015 16:05:29 +0700 In-Reply-To: <83a8yx1tgw.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 28 Mar 2015 10:17:35 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a01:4f8:d15:1b86::2 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:184445 Archived-At: >>>>> Eli Zaretskii writes: >>>>> From: Stefan Monnier Date: Fri, 27 Mar 2015 18:34:36 -0400 >> If someone provides a patch to add an optional new behavior to >> vc-next-action, it'll probably be accepted (as long as it's clean >> enough). And as long as noone writes such a patch this discussion >> is just hot air. > How many people even use vc-next-action these days? With Git, I use it strictly as a substitute for the (otherwise unavailable) vc-commit. > IOW, would it be okay to make it work very differently for modern > dVCSes than what it does now? > For example, in a Git repository where "git status" shows nothing, > vc-next-action invoked without an argument currently says "Fileset is > up-to-date" and does nothing, which is IMO less than useful. Would > someone mind if it suggested a "git pull" instead? > Also, there's no handling of pull problems, and the handling of > conflicts is rudimentary at best. And, of course, there's no support > at all for pushing; there's no notion of local commits that are > missing upstream. Would someone mind if vc-next-action were changed > in these regards? My Git usage is neither typical nor exemplary, but I both git-fetch(1) and git-push(1) from outside of the chroot environments I use for development. (If only because such environments lack access to the relevant SSH keys.) I have no objections against such features as long as they=E2=80=99re optional and never affect the vc-commit function I use. And should they come to be /not/ optional, I guess I=E2=80=99d be able to bear with them, either. --=20 FSF associate member #7257 http://boycottsystemd.org/ =E2=80=A6 3013 B6A0= 230E 334A