From: Pavel Roskin <proski@gnu.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: "git add $ignored_file" fail
Date: Wed, 17 May 2006 15:23:06 -0400 [thread overview]
Message-ID: <1147893786.16654.5.camel@dv> (raw)
In-Reply-To: <e4f9eo$b60$1@sea.gmane.org>
On Wed, 2006-05-17 at 15:46 +0200, Jakub Narebski wrote:
> Santi wrote:
>
> > In the other way, now I find the value of being able to say:
> >
> > $ git add t*
> >
> > and be sure that it does not add an ignored file. Unfortunately
> > git-add cannot distinguish between both.
>
> Well, it could. If 'git add <filespec>' would result in NO files
> added, take <filespec> as literate <file> (filename), regardless
> of ignores.
Can we apply the ignore rules to the directories but not the files?
This way, "git-add *" would add all files (rarely a good idea), whereas
"git-add ." would respect the ignore rules.
Kludgy as it is, this approach would generally produce more expected
results than others. If you let the shell expand the pattern, expect
all junk to be added. If you let git expand the pattern, expect it to
adhere to the ignore rules.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-05-17 19:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 22:07 "git add $ignored_file" fail Santi
2006-05-16 22:28 ` Linus Torvalds
2006-05-16 22:41 ` Jakub Narebski
2006-05-16 22:42 ` Santi
2006-05-17 11:08 ` Johannes Schindelin
[not found] ` <81b0412b0605170604i689a8f7axa5aeb7752dc72072@mail.gmail.com>
2006-05-17 13:41 ` Santi
2006-05-17 13:46 ` Jakub Narebski
2006-05-17 19:23 ` Pavel Roskin [this message]
[not found] ` <20060517153903.6b896fdd.seanlkml@sympatico.ca>
2006-05-17 19:39 ` Sean
2006-05-17 19:52 ` Jakub Narebski
2006-05-17 19:56 ` Pavel Roskin
2006-05-17 20:26 ` Linus Torvalds
2006-05-17 20:35 ` Jakub Narebski
2006-05-17 20:53 ` Linus Torvalds
2006-05-17 23:07 ` Junio C Hamano
2006-05-17 23:20 ` Linus Torvalds
2006-05-17 13:48 ` Johannes Schindelin
2006-05-17 14:49 ` 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=1147893786.16654.5.camel@dv \
--to=proski@gnu.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.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).