git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Santi Béjar" <santi@agolina.net>
To: Gianluca Pacchiella <gianluca.pacchiella@ktln2.org>
Cc: git@vger.kernel.org
Subject: Re: Checkout of orphan branch files into mainline worktree
Date: Thu, 25 Mar 2010 12:10:20 +0100	[thread overview]
Message-ID: <adf1fd3d1003250410w5bd79777h77e1923e5a4b19dd@mail.gmail.com> (raw)
In-Reply-To: <hofehl$jbn$1@dough.gmane.org>

On Thu, Mar 25, 2010 at 11:39 AM, Gianluca Pacchiella
<gianluca.pacchiella@ktln2.org> wrote:
> Hi folks,
>
> I have a repository where I maintain a project for a web site with a branch
> (disconnected from the mainline history) that contains some files
> (necessary only for a particular instance of a site) that don't intersect
> with others files in the main project. Since I don't want to use submodule
> and subtree I manage myself to this sequence of commands ("deploy" is the
> branch name of the mainline history and "index" of the --orphan branch) to
> checkout the index's files into the mainline files
>
> git read-tree index && ( git ls-files --with-tree=index | git
> checkout-index --stdin ) && git read-tree deploy
>
> Are there some other ways to do this? I'm crazy? are there side effects?

I don´t know if this is a good idea in general, but you could get the
same result with:

git merge --no-commit index &&
git reset deploy

HTH,
Santi

>
> Thanks,
>        Gianluca
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

      reply	other threads:[~2010-03-25 11:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25 10:39 Checkout of orphan branch files into mainline worktree Gianluca Pacchiella
2010-03-25 11:10 ` Santi Béjar [this message]

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=adf1fd3d1003250410w5bd79777h77e1923e5a4b19dd@mail.gmail.com \
    --to=santi@agolina.net \
    --cc=gianluca.pacchiella@ktln2.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 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).