From: Kevin Daudt <me@ikke.info>
To: Olga Pshenichnikova <olga@ip-5.ru>
Cc: git@vger.kernel.org
Subject: Re: How to include just some subdirectory excluding all envelop tree
Date: Mon, 7 Mar 2016 22:06:09 +0100 [thread overview]
Message-ID: <20160307210608.GA29312@ikke.info> (raw)
In-Reply-To: <56DDD020.2050101@ip-5.ru>
On Mon, Mar 07, 2016 at 10:01:52PM +0300, Olga Pshenichnikova wrote:
> I have some tree structure:
>
> /a
> /a/a
> /a/b
> ..
> /a/z
> /b
> .. (thousands of folders)
> /z
>
> How can I control just /a/a folder?
> What exclude file should be?
>
> The way we use now is:
>
> /a/*
> /b/
> .. (thousands of folders)
> /z/
> !/a/a
>
> But it is very not nice looking and hard for maintenance...
Don't know your usecase, but isn't it easier to just create the repository
in /a/a? Then you won't have to exlude anything.
If you must, you can just use something like:
*
!/a
/a/*
!/a/a
next prev parent reply other threads:[~2016-03-07 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-07 19:01 How to include just some subdirectory excluding all envelop tree Olga Pshenichnikova
2016-03-07 21:06 ` Kevin Daudt [this message]
2016-03-07 21:14 ` Olga Pshenichnikova
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=20160307210608.GA29312@ikke.info \
--to=me@ikke.info \
--cc=git@vger.kernel.org \
--cc=olga@ip-5.ru \
/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).