git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Radoslaw Szkodzinski <astralstorm@gorzow.mm.pl>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Quick question
Date: Tue, 14 Feb 2006 02:50:46 +0100	[thread overview]
Message-ID: <43F13776.9000501@gorzow.mm.pl> (raw)
In-Reply-To: <7vy80eydq0.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

Junio C Hamano wrote:
> With the git.git repository itself, I tried:
> 
> $ cat /var/tmp/i
> *.c
> $ git ls-files -i -X /var/tmp/i | head -n 6
> apply.c
> arm/sha1.c
> blob.c
> cat-file.c
> check-ref-format.c
> checkout-index.c
> 
> So I am not sure what you mean.  You wanted to "display ignored
> files of the whole project", right?  I am getting arm/sha1.c
> here in my output, so I do not understand the issue here...
> 

Wrong. I wanted to display files that are ignored and not checked in.
(unlike your example)

That's why I used the -o (--others).

Try your example with git repo's .gitignore and any .o file.
I would like to use it for backup~ hunting purposes in a script
and not have to worry about find and other less portable tools.

-- 
GPG Key id:  0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0  9105 9543 0453 D1F1 0BA2

AstralStorm


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

  reply	other threads:[~2006-02-14  1:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-13 16:36 Quick question Radoslaw Szkodzinski
2006-02-13 16:54 ` Linus Torvalds
2006-02-13 18:26   ` Radoslaw Szkodzinski
2006-02-13 20:17     ` Alex Riesen
2006-02-14  7:52   ` Junio C Hamano
2006-02-14  0:40 ` Junio C Hamano
2006-02-14  1:50   ` Radoslaw Szkodzinski [this message]
2006-02-14  2:03     ` Junio C Hamano
2006-02-14  2:21       ` Radoslaw Szkodzinski
  -- strict thread matches above, loose matches on Subject: below --
2012-03-01 19:00 Quick Question Max Lucchetti
2012-03-01 19:35 ` Junio C Hamano
2012-03-01 19:45   ` Max Lucchetti

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=43F13776.9000501@gorzow.mm.pl \
    --to=astralstorm@gorzow.mm.pl \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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).