From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: [PATCH] little fixes for attachment git commiting Date: Fri, 19 Feb 2010 12:03:28 +0100 Message-ID: References: <87635xuhnd.fsf@dasa3.iem.pw.edu.pl> <0E4FD6B3-1912-4A6B-96A1-0CF00B3EAED1@gmail.com> <873a0xv6c2.fsf@dasa3.iem.pw.edu.pl> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=UTF-8; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NiQf8-0005Gk-F9 for emacs-orgmode@gnu.org; Fri, 19 Feb 2010 06:04:46 -0500 Received: from [140.186.70.92] (port=39186 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NiQf2-0005EA-4z for emacs-orgmode@gnu.org; Fri, 19 Feb 2010 06:04:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NiQdu-0004wU-E1 for emacs-orgmode@gnu.org; Fri, 19 Feb 2010 06:03:31 -0500 Received: from mail-ew0-f224.google.com ([209.85.219.224]:37481) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NiQdu-0004wI-9X for emacs-orgmode@gnu.org; Fri, 19 Feb 2010 06:03:30 -0500 Received: by ewy24 with SMTP id 24so3497367ewy.26 for ; Fri, 19 Feb 2010 03:03:29 -0800 (PST) In-Reply-To: <873a0xv6c2.fsf@dasa3.iem.pw.edu.pl> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: =?UTF-8?Q?=C5=81ukasz_Stelmach?= Cc: emacs-orgmode@gnu.org On Feb 19, 2010, at 11:59 AM, =C5=81ukasz Stelmach wrote: > Carsten Dominik writes: > >> On Feb 16, 2010, at 8:04 PM, =C5=81ukasz Stelmach wrote: >> >>> There are two very small commits which iron some wrinkles. Both on >>> org-attach-git-commit branch of >>> git://github.com/steelman/steelman-org-mode.git >>> >>> The first prevents git from running on an empty set of deleted =20 >>> files. >> >> Why is that a problem? I am hesitating to apply this patch, because >> on my Mac OS 10.5, xargs does know the --no-run-if-empty argument. > ^^^^^^^^^[*] > > When xargs launches git rm without file arguments git emmits usage > > --8<---------------cut here---------------start------------->8--- > usage: git rm [options] [--] ... > > -n, --dry-run dry run > -q, --quiet be quiet > --cached only remove from the index > -f, --force override the up-to-date check > -r allow recursive removal > --ignore-unmatch exit with a zero status even if nothing > -matched > --8<---------------cut here---------------end--------------->8--- > > message which in this situation is a bit confusing and *suggests* > somehting might have gone wrong. And of course a shell output buffer > pops up. > > [*] does || doesn't? Does not. Do you actually get to see this error message? Where? - Carsten