From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Compilation problem Date: Tue, 18 Sep 2012 15:28:44 +0200 Message-ID: <18649054-2DC5-4BFE-A361-F5DC457BFDF1@gmail.com> References: <5986.1347306768@alphaville.americas.hpqcorp.net> <87wr01hc4f.fsf@Rainer.invalid> <87lighr5xf.fsf@altern.org> <87pq5thbno.fsf@Rainer.invalid> <87har5r5iv.fsf@altern.org> <87wr01sdsu.fsf@gmail.com> <87boh331py.fsf@bzg.ath.cx> Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:36502) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TDxrE-00034a-LA for emacs-orgmode@gnu.org; Tue, 18 Sep 2012 09:29:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TDxr6-0005Xo-3J for emacs-orgmode@gnu.org; Tue, 18 Sep 2012 09:28:56 -0400 Received: from mail-ee0-f41.google.com ([74.125.83.41]:56329) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TDxr5-0005Xk-Ta for emacs-orgmode@gnu.org; Tue, 18 Sep 2012 09:28:48 -0400 Received: by eeke49 with SMTP id e49so4664667eek.0 for ; Tue, 18 Sep 2012 06:28:46 -0700 (PDT) In-Reply-To: <87boh331py.fsf@bzg.ath.cx> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Bastien Cc: Achim Gratz , emacs-orgmode@gnu.org, Jambunathan K On 18.9.2012, at 15:22, Bastien wrote: > Hi Jambunathan, >=20 > Jambunathan K writes: >=20 >> Please ask for clarification and politely indicate that a change may >> have to be reverted. =20 >=20 > Sorry that I reverted this one too hastily and without warning. >=20 >> Instead of the commit being wrong, is it possible that >> changes were incomplete. =20 >=20 > I understand. >=20 > What would be helpful would be some comment in the commit telling=20 > that the change is part of a bigger change that is not yet committed. >=20 > But I think we should try to avoid this: the whole point of using git=20= > is to commit changes only if they are complete. Hi Bastien, I think this should be to *merge* (and push) only complete changes. At = least this is what I think - git allows you to commit often while making = changes. Actually, I think you agree, your next paragraph says as much. - Carsten > A "change" can be a > commit or a set of commits, but let's try to push changes only when > they are complete. >=20 > I know this is not always easy, and I'm not lecturing here, I'm just > sharing directions I try to follow myself. >=20 > Thanks, >=20 > --=20 > Bastien >=20