From: Andreas Gal <gal@uci.edu>
To: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
Cc: GIT <git@vger.kernel.org>
Subject: Re: list all dirty files in working directory
Date: Thu, 5 May 2005 14:35:05 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0505051433190.8745@sam.ics.uci.edu> (raw)
In-Reply-To: <20050505212152.GP20994@cip.informatik.uni-erlangen.de>
git-update-cache --refresh | while read line; do
echo $line | cut -d ':' -f 1
done
That should give you one file per line, for every dirty file.
Andreas
On Thu, 5 May 2005, Thomas Glanzmann wrote:
> Hello,
> is there another way than call 'checkout-cache -a' and parse the output?
> Maybe a command which lists one dirty file per line?
>
> Thomas
> -
> 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
>
next prev parent reply other threads:[~2005-05-05 21:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 21:21 list all dirty files in working directory Thomas Glanzmann
2005-05-05 21:32 ` Thomas Glanzmann
2005-05-05 21:35 ` Andreas Gal [this message]
2005-05-06 2:06 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0505051433190.8745@sam.ics.uci.edu \
--to=gal@uci.edu \
--cc=git@vger.kernel.org \
--cc=sithglan@stud.uni-erlangen.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).