From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Hendy <jw.hendy@gmail.com>
Subject: Re: Assistance with patching instructions on Worg
Date: Fri, 31 Jan 2014 16:34:15 -0600
Message-ID: <CA+M2ft_52tnY-G_fsBLkwmfNiK6-cv_ST3fyX2QAdG-aTkJ2=Q@mail.gmail.com>
References: <CA+M2ft8dGaGT-PpbL3nyb+4beAQtpxmtwvFK8PdzWF884p9-SA@mail.gmail.com>
	<87y51veqo3.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59251)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jw.hendy@gmail.com>) id 1W9MfB-00081v-R2
	for emacs-orgmode@gnu.org; Fri, 31 Jan 2014 17:34:18 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <jw.hendy@gmail.com>) id 1W9MfA-0007P5-Ou
	for emacs-orgmode@gnu.org; Fri, 31 Jan 2014 17:34:17 -0500
Received: from mail-ob0-x22e.google.com ([2607:f8b0:4003:c01::22e]:43947)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <jw.hendy@gmail.com>) id 1W9MfA-0007OV-HQ
	for emacs-orgmode@gnu.org; Fri, 31 Jan 2014 17:34:16 -0500
Received: by mail-ob0-f174.google.com with SMTP id uy5so5677457obc.19
	for <emacs-orgmode@gnu.org>; Fri, 31 Jan 2014 14:34:15 -0800 (PST)
In-Reply-To: <87y51veqo3.fsf@gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=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: Josiah Schwab <jschwab@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>

On Fri, Jan 31, 2014 at 4:23 PM, Josiah Schwab <jschwab@gmail.com> wrote:
>
> jw.hendy@gmail.com writes:
>
>> emacs doc/org.texi
>>
>> [make changes to documentation]
>>
>> git commit -m "Update documentation to org-src-preserve-indentation."
>>
>> git format-patch master
>>
>> But no files were generated... Am I doing something incorrectly?
>
> Yes.  You need to explicitly add your changes to the index.
>
>   git add doc/org.text
>
> then git commit -m "message" will behave as you expect.
>
> (Using "git commit -a" worked, because that is like doing a "git add" to
> all modified files.)
>
> It sounds like you misunderstand what "git add" does.  If you read a
> little bit more about git workflows, I think it will make sense to you.

Perhaps, though I'm familiar with `git -am "comment"` on my own stuff.
I was just following along with Worg, which doesn't mention doing
that. I'm now thinking that `git add` must be implied in the line
=make some changes (1)=?


John

>
> Perhaps the following link would be useful:
> http://stackoverflow.com/questions/3689838/difference-between-head-working-tree-index-in-git
>
> Hope that helps,
> Josiah
>