list of files that have been added/removed

list of files that have been added/removed

[layer]

I see the changes in the index with "git status" as "deleted" or
"added".  What command wlil print just the filenames.  I've been
searching and searching and no luck.   Thanks!

Kevin

Re: list of files that have been added/removed

[layer]

  I see the changes in the index with "git status" as "deleted" or
  "added".  

I meant "new file" here.  Of course I can process the output of "git
status", but I was looking for a cleaner method, if there is one.

Thanks.

Kevin

Re: list of files that have been added/removed

[Eric Raible]

layer <layer <at> known.net> writes:

> 
>   I see the changes in the index with "git status" as "deleted" or
>   "added".  
> 
> I meant "new file" here.  Of course I can process the output of "git
> status", but I was looking for a cleaner method, if there is one.
> 
> Thanks.
> 
> Kevin
> 

Perhaps:
git diff --name-only

Re: list of files that have been added/removed

[Junio C Hamano]

layer <layer@known.net> writes:

>   I see the changes in the index with "git status" as "deleted" or
>   "added".  
>
> I meant "new file" here.  Of course I can process the output of "git
> status", but I was looking for a cleaner method, if there is one.

"Process" as in "Read in a script and have it act on the information"?

git diff-index --name-status HEAD

would be one Kosher way for the scripts, and if your scripting language
can handle NUL terminated string, giving -z option would make your script
more robust against funny pathnames.

git diff-index --name-only --diff-filter=A HEAD

if you only care about "new file" and nothing else.

Re: list of files that have been added/removed

[layer]

Junio C Hamano <gitster@pobox.com> wrote:

>> layer <layer@known.net> writes:
>> 
>> >   I see the changes in the index with "git status" as "deleted" or
>> >   "added".  
>> >
>> > I meant "new file" here.  Of course I can process the output of "git
>> > status", but I was looking for a cleaner method, if there is one.
>> 
>> "Process" as in "Read in a script and have it act on the
>> information"?

Yes.  Junio, your answer was perfect.  Thanks.

>> 
>> git diff-index --name-status HEAD
>> 
>> would be one Kosher way for the scripts, and if your scripting language
>> can handle NUL terminated string, giving -z option would make your script
>> more robust against funny pathnames.
>> 
>> git diff-index --name-only --diff-filter=A HEAD
>> 
>> if you only care about "new file" and nothing else.
>> 
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html