From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>,
"Victor Bogado da Silva Lins" <victor@bogado.net>,
"Sean Estabrooks" <seanlkml@sympatico.ca>,
git@vger.kernel.org
Subject: Re: how to git-archive ignore some files?
Date: Mon, 12 May 2008 02:36:33 -0700 (PDT) [thread overview]
Message-ID: <m3prrr50gc.fsf@localhost.localdomain> (raw)
In-Reply-To: <7vwsm06cdd.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> René Scharfe <rene.scharfe@lsrfire.ath.cx> writes:
>
> > Another idea: would it make sense to have an attribute for that instead
> > (or in addition to the command line parameter)? I.e. files marked
> > export-ignore would not end up in the archive. I suspect the set of
> > files to ignore doesn't change from archive to archive one creates.
>
> That sounds extremely sensible.
>
> Should/does git-archive read .gitattributes from the tree being exported?
If I understand and remember correctly, current implementation of
gitattributes, and current tools (git-check-attr), use and can use
only working directory version of .gitattributes, in part because of
chicken-and-egg problem (attributes effect checkout) IIRC.
It would be nice if git-archive read and use .gitattribues from
a tree being exported; this would for example make `export-subs`
work even for bare repositories. This would be needed for
`export-ignore`.
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2008-05-12 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 18:15 how to git-archive ignore some files? Victor Bogado da Silva Lins
2008-05-06 18:56 ` Sean Estabrooks
2008-05-06 21:23 ` René Scharfe
2008-05-06 22:08 ` Junio C Hamano
2008-05-11 10:44 ` René Scharfe
2008-05-11 16:20 ` Junio C Hamano
2008-05-12 9:36 ` Jakub Narebski [this message]
2008-06-08 16:42 ` René Scharfe
2008-05-08 17:04 ` David Bryson
2008-05-08 20:22 ` Johannes Schindelin
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=m3prrr50gc.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=rene.scharfe@lsrfire.ath.cx \
--cc=seanlkml@sympatico.ca \
--cc=victor@bogado.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).