From: Jakub Narebski <jnareb@gmail.com>
To: Yakup Akbay <yakbay@ubicom.com>
Cc: git@vger.kernel.org
Subject: Re: Feature Request: Capability to save and load the workspace
Date: Fri, 31 Jul 2009 02:20:25 -0700 (PDT) [thread overview]
Message-ID: <m3prbhryn7.fsf@localhost.localdomain> (raw)
In-Reply-To: <4A72AF1C.1020500@ubicom.com>
Yakup Akbay <yakbay@ubicom.com> writes:
> I'm not sure whether such a feature exists or not. But let me explain my
> concern.
>
> Say, we have different profiles for different products. When I work on a
> profile (edit, configure, build etc.) I can't switch to another profile
> before I distclean the existing one. So, when I have to work on 2
> projects at the same time, I have to have 2 copies of the same source
> tree. This might be OK for 2, but if the repository is around 3 gigs
> this is not quite suitable for more than 2 profiles.
>
> IT WOULD BE NICE to have a feature in git that allows us to save the
> current workspace then work on a different profile on a clean
> environment. Then save that profile and switch back to the previous
> profile at any time without losing the environment.
First, if the problem is repository size, you can use git-new-workdir
script from contrib/ to have multiple checkouts for a single
repository (but each checkout better be on different branch).
As to "save current state": take a look at 'git stash' command, which
saves state of working directory (and index).
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-07-31 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 8:45 Feature Request: Capability to save and load the workspace Yakup Akbay
2009-07-31 9:09 ` Erik Faye-Lund
2009-07-31 9:16 ` Yakup Akbay
2009-07-31 10:14 ` Johannes Schindelin
2009-07-31 12:08 ` Matthieu Moy
2009-07-31 9:20 ` Jakub Narebski [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=m3prbhryn7.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=yakbay@ubicom.com \
/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).