All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Todd A. Jacobs" <nospam@codegnome.org>
To: git@vger.kernel.org
Subject: git-archive ignores export-ignore
Date: Thu, 21 Jan 2010 14:13:12 -0800	[thread overview]
Message-ID: <20100121221312.GB5307@penguin.codegnome.org> (raw)

Using git 1.6.4.2, the manual page prophesies that:

    Files and directories with the attribute export-ignore won't be
    added to archive files. See gitattributes(5) for details.

However, various tools seem to be unhappy about this attribute. In
particular, checkout complains about invalid attributes:

    $ cat .gitattributes
    *.py export-subst
    *.html export-subst
    juniperxml.cfg export-ignore

    $ git checkout juniperxml.cfg
    export-ignore is not a valid attribute name: .gitattributes:3

It appears that git-archive doesn't seem to respect the attribute
either. Consider the following example:

    cd /tmp
    mkdir foo
    cd foo
    git init
    touch foo.sh
    echo '*sh' > .gitattributes
    git add foo.sh
    git add .gitattributes
    git commit -m test
    git archive HEAD
    pax_global_header00006660000000000000000000000064113261226070014512gustar00rootroot0000000000000052 comment=202d78e6a44c7f10bee2ad96a3b2adc80fc33468
    .gitattributes000066400000000000000000000000041132612260700137430ustar00rootroot00000000000000*sh
    foo.sh000066400000000000000000000000001132612260700121630ustar00rootroot00000000000000

In addition to whatever bugs there might be in reading and applying the
attributes correctly, it would seem that the man page could be a bit
clearer on how and where to apply the attributes.

Assuming PEBKAC for the moment, how can I get the behavior I'm
expecting?

-- 
"Oh, look: rocks!"
	-- Doctor Who, "Destiny of the Daleks"

             reply	other threads:[~2010-01-22  0:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-21 22:13 Todd A. Jacobs [this message]
2010-01-22  0:57 ` git-archive ignores export-ignore Junio C Hamano
2010-01-22 18:07   ` Todd A. Jacobs

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=20100121221312.GB5307@penguin.codegnome.org \
    --to=nospam@codegnome.org \
    --cc=git@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.