On Wed, 2012-10-10 at 14:47 -0700, Junio C Hamano wrote:
> Drew Northup <drew.nort...@maine.edu> writes:
> > # Untracked files:
> > # (use "git add <file>..." to include in what will be committed)
> > #
> > # rc.d/rc2.d/S08iptables
> > # rc.d/rc3.d/S08iptables
> > # rc.d/rc4.d/S08iptables
> > ...
> > no changes added to commit (use "git add" and/or "git commit -a")
> > It detects the changes as renames however―which in this case isn't
> > appropriate:
> > [root@drew-northup ~]# etckeeper vcs status
> > # On branch master
> > # Changes to be committed:
> > # (use "git reset HEAD <file>..." to unstage)
> > #
> > # renamed: rc.d/rc2.d/K92iptables -> rc.d/rc2.d/S08iptables
> > # renamed: rc.d/rc3.d/K92iptables -> rc.d/rc3.d/S08iptables
> > # renamed: rc.d/rc4.d/K92iptables -> rc.d/rc4.d/S08iptables
> > #...
> Given that all of these six files have the same contents, I actually
> am slightly impressed how well Git matched them up ;-).
> But more seriously, why do you have rc.d/rc2.d/S08iptables untracked
> in the working tree but in the index to be committed?
Missing steps in the mail body: etckeeper vcs add <File> & etckeeper vcs
rm <File> commands. I pared it back to the absolute minimum.
Is that what you're asking about?
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html