From: Willy Tarreau <w@1wt.eu>
To: Chase Venters <chase.venters@clientec.com>
Cc: linux-kernel@vger.kernel.org, git@vger.kernel.org
Subject: Re: Question about your git habits
Date: Sat, 23 Feb 2008 09:56:34 +0100 [thread overview]
Message-ID: <20080223085634.GW8953@1wt.eu> (raw)
In-Reply-To: <200802221837.37680.chase.venters@clientec.com>
On Fri, Feb 22, 2008 at 06:37:14PM -0600, Chase Venters wrote:
> It seems to me that having multiple working trees (effectively, cloning
> the "master" repository every time I need to make anything but a trivial
> change) would be most effective under git as well as it doesn't require
> creating messy, intermediate commits in the first place (but allows for them
> if they are used). But I wonder how that approach would scale with a project
> whose git repo weighed hundreds of megs or more. (With a centralized rcs, of
> course, you don't have to lug around a copy of the whole project history in
> each working tree.)
Take a look at git-new-workdir in git's contrib directory. I'm using it a
lot now. It makes it possible to set up as many workdirs as you want, sharing
the same repo. It's very dangerous if you're not rigorous, but it saves a lot
of time when you work on several branches at a time, which is even more true
for a project's documentation. The real thing to care about is not to have
the same branch checked out at several places.
Regards,
Willy
next prev parent reply other threads:[~2008-02-23 8:57 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 0:37 Question about your git habits Chase Venters
2008-02-23 1:26 ` Tommy Thorn
2008-02-23 1:28 ` Steven Walter
2008-02-23 1:37 ` Jan Engelhardt
2008-02-23 1:44 ` Al Viro
2008-02-23 1:51 ` Junio C Hamano
2008-02-23 2:09 ` Al Viro
[not found] ` <998d0e4a0802221823h3ba53097gf64fcc2ea826302b@mail.gmail.com>
2008-02-23 2:47 ` J.C. Pizarro
2008-02-23 11:39 ` Charles Bailey
2008-02-23 13:08 ` J.C. Pizarro
2008-02-23 13:17 ` Charles Bailey
2008-02-23 13:36 ` J.C. Pizarro
2008-02-23 14:01 ` Charles Bailey
2008-02-23 17:10 ` J.C. Pizarro
2008-02-23 18:16 ` Charles Bailey
2008-02-23 18:47 ` J.C. Pizarro
2008-02-23 19:28 ` Charles Bailey
2008-02-23 18:19 ` J.C. Pizarro
2008-02-23 14:08 ` Mike Hommey
2008-02-23 1:42 ` Junio C Hamano
2008-02-23 10:39 ` Samuel Tardieu
[not found] ` <998d0e4a0802221736q4e4c3a28l101522912f7d3caf@mail.gmail.com>
2008-02-23 2:46 ` J.C. Pizarro
2008-02-23 4:10 ` Daniel Barkalow
2008-02-23 5:03 ` Jeff Garzik
2008-02-23 9:18 ` Mike Hommey
2008-02-23 4:39 ` Rene Herman
2008-02-23 8:56 ` Willy Tarreau [this message]
2008-02-23 9:10 ` Sam Ravnborg
2008-02-23 13:07 ` Jakub Narebski
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=20080223085634.GW8953@1wt.eu \
--to=w@1wt.eu \
--cc=chase.venters@clientec.com \
--cc=git@vger.kernel.org \
--cc=linux-kernel@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).