From: "Ciprian Dorin Craciun" <ciprian.craciun@gmail.com>
To: "Julian Phillips" <julian@quantumfyre.co.uk>,
"Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Exporting a tree from a repository
Date: Sun, 15 Jul 2007 10:12:08 +0300 [thread overview]
Message-ID: <8e04b5820707150012r13c5db69g96b97d910dc1b137@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707142237190.13310@beast.quantumfyre.co.uk>
On 7/15/07, Julian Phillips <julian@quantumfyre.co.uk> wrote:
> On Sat, 14 Jul 2007, Ciprian Dorin Craciun wrote:
>
> > Hello all!
> >
> > I am a new GIT user, I like it, so I started playing with it for
> > different projects I work on.
> >
> > Currently I am playing with "Linux from Scratch", and I have
> > written some scripts to automatize the build process -- kind of
> > install scripts...
> >
> > For this I use GIT to store all the source packages -- each inside
> > it's own branch :).
> >
> > My question is the following: How can I export an entire tree
> > without using a working directory, or cloning the repository. (Because
> > from what I have seen so far there is no way to use the same
> > repository with many working directories...)
>
> You can have as many working directories as you want from one repository
> using the git-new-workdir script from contrib/workdir. You do need to be
> careful when updating references though (you basically want to avoid
> updating a reference that you are using in another working directory).
>
> You should also be able to use this to get an "export" - simply create the
> new workdir and then remove the .git (being careful not to accidentally do
> this in your actual repository). However I expect there is a better way
> to do this ...
>
> --
> Julian
>
> ---
> Quark! Quark! Beware the quantum duck!
Thank you for the hint about git-new-workdir! I will try it.
Now for the export thing... I know that I can just clone the
remote repository and then remove the .git folder, but for my purpose
I just want to have the HEAD tree downloaded, without any history...
And by using git clone I end up downloading much more than I actually
need.
I am looking for a feature like 'svn export <repo+tree_path>
<destination_path>'...
Ciprian.
next prev parent reply other threads:[~2007-07-15 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 20:25 Exporting a tree from a repository Ciprian Dorin Craciun
2007-07-14 21:46 ` Julian Phillips
2007-07-15 6:12 ` Junio C Hamano
2007-07-15 7:12 ` Ciprian Dorin Craciun [this message]
2007-07-15 9:15 ` Alex Riesen
2007-07-15 7:17 ` martin f krafft
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=8e04b5820707150012r13c5db69g96b97d910dc1b137@mail.gmail.com \
--to=ciprian.craciun@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=julian@quantumfyre.co.uk \
/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