[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Ranger-users] Re: doc updates to pull

From: Roman Z.
Subject: Re: [Ranger-users] Re: doc updates to pull
Date: Fri, 30 Apr 2010 19:10:01 +0200
User-agent: Mutt/1.5.20 (2009-06-14)

On Fri, Apr 30, 2010 at 09:17:42AM +0530, Sitaram Chamarty wrote:
> On Fri, Apr 30, 2010 at 8:22 AM, Roman Z. <address@hidden> wrote:
> >> I'm attaching a doc update patch that you can apply using "git am" if you 
> >> like.
> >
> > Done, thank you.
> >
> > Are the whitespace changes intentional?  (I mean the lines
> > "(again, this is equivalent to [...]" and "process (flag D) [...]")
> > http://git.savannah.gnu.org/cgit/ranger.git/commit/?id=02bd7c4f53
> hmm no... I didn't even notice.
> Let me explain what may have happened.
> I don't use hard tabs anywhere in my docs and my vim settings are set
> that way.  I am also not a python guy, so I played safe by running all
> files I changed through "unexpand" to put tabs back before saving the
> files.
> It looks as though the files originally had hard tabs everywhere
> *except* just those 2 lines.
> The apparent reduction of one space in the diff output is also due to
> a series of spaces being replaced by a tab -- with the extra "-" or
> "+" in the new column 1, those lines will *look* like they have
> shifted left compared to the originals that used actual spaces.  If
> you look in the actual file you will see they line up ok.
> Sorry about all that; let me know if it makes a difference, and next
> time I'll run unexpand only on lines I touch.
> Sitaram

No worries, it makes no difference and even if, I could revert it.

Git allows you to choose what exactly to commit, for example if you use
"git citool", right click on the text and click on "Stage Hunk for
Commit" and only that will be commited.  I use that all the time :)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]