git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Mark Burton" <markb@ordern.com>
Cc: git@vger.kernel.org
Subject: Re: How to list versioned files with modification status
Date: Sun, 5 Oct 2008 00:34:31 +0200	[thread overview]
Message-ID: <81b0412b0810041534o7b38507qe63db47cd07fdc16@mail.gmail.com> (raw)
In-Reply-To: <loom.20081004T215458-15@post.gmane.org>

2008/10/5 Mark Burton <markb@ordern.com>:
> Alex Riesen <raa.lkml <at> gmail.com> writes:
>> 2008/10/4 Mark Burton <markb <at> smartavionics.com>:
>> > I would like to be able to easily find those files in a git tree that
>> > don't have pending modifications. Although ls-files can list the
>> > files that are modified, it can't list those that aren't or list all
>> > files with their modification status.
>>
>> Maybe if you look at git diff and diff-index,  you will find something
>> what suits you better? Because "modification" is just a difference
>> between a known (recorded in a commit or index) state and your
>> working tree.
>
> 'git diff --name-status' looks useful but it only shows the files that have
> changed - I would like to see the names of the files that haven't changed.

There is nothing to do something like that, but...

> Even svn could do that (svn status).

what exactly are trying to achieve? It is just strange that no one
asked for something like this before...

  reply	other threads:[~2008-10-04 22:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-04 12:12 How to list versioned files with modification status Mark Burton
2008-10-04 21:40 ` Alex Riesen
2008-10-04 22:09   ` Mark Burton
2008-10-04 22:34     ` Alex Riesen [this message]
2008-10-04 22:52       ` deskinm
2008-10-04 23:02       ` Mark Burton
2008-10-04 23:10     ` Linus Torvalds
2008-10-05  9:04       ` Mark Burton
2008-10-04 23:09 ` Dmitry Potapov

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=81b0412b0810041534o7b38507qe63db47cd07fdc16@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=markb@ordern.com \
    /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).