From: shawn wilson <ag4ve.us@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Konstantin Khomoutov <kostix+git@007spb.ru>,
Git List <git@vger.kernel.org>
Subject: Re: split directories into branches
Date: Mon, 4 Jul 2016 19:31:49 -0400 [thread overview]
Message-ID: <CAH_OBidRkhGZ2yjAxGkvw=36PLtOACvHFuyKZxFZruTAtDwxiQ@mail.gmail.com> (raw)
In-Reply-To: <CAH_OBieNO-fSW-ncsezZ5KG2c80fY-rUU6OPGgw0RJMGcpi+KQ@mail.gmail.com>
correction
On Mon, Jul 4, 2016 at 7:30 PM, shawn wilson <ag4ve.us@gmail.com> wrote:
> shopt -s extglob; declare -a f=(!(cookbooks)); git filter-branch
> --tree-filter "mkdir -p cookbooks/base_sys && mv ${f[@]}
> cookbooks/base_sys"
>
next prev parent reply other threads:[~2016-07-04 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 16:45 split directories into branches shawn wilson
2016-07-04 17:39 ` Konstantin Khomoutov
2016-07-04 18:15 ` shawn wilson
2016-07-04 18:29 ` Konstantin Khomoutov
2016-07-04 21:03 ` shawn wilson
2016-07-04 22:10 ` Andreas Schwab
2016-07-04 23:30 ` shawn wilson
2016-07-04 23:31 ` shawn wilson [this message]
2016-07-05 9:56 ` Konstantin Khomoutov
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='CAH_OBidRkhGZ2yjAxGkvw=36PLtOACvHFuyKZxFZruTAtDwxiQ@mail.gmail.com' \
--to=ag4ve.us@gmail.com \
--cc=git@vger.kernel.org \
--cc=kostix+git@007spb.ru \
--cc=schwab@linux-m68k.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 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).