Re: Why doesn't git commit -a track new files

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

 



Matthieu Moy venit, vidit, dixit 24.02.2011 17:04:
> Michael J Gruber <git@xxxxxxxxxxxxxxxxxxxx> writes:
> 
>> Why does it not exist? Because you should at least
>> "git add -A && git status && behappy && git commit".
> 
> There are alternatives like
> 
> git status && behappy && git commit -A

That may not give the full picture of untracked stuff in subdirs.

> or
> 
> git commit -A && look at status $EDITOR && behapy && save

Yes, I even mentioned that, but you cut it. Bad bad boy! ;)

>> Also, "-A" supports a very "un-gitty" way of using git. This makes it
>> unlikely that someone cares to implement it...
> 
> I guess that's it. It's not usefull to most Git developers, hence nobody
> cared to implement it. But IIRC the switch "add -A" was chosen partly
> because -A didn't exist for commit, hence this leaves room for commit

Yes.

So, we have one more volunteer for the plan just laid out, right?

Michael
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]