From: Samuel Tardieu <sam@rfc1149.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Chase Venters <chase.venters@clientec.com>, git@vger.kernel.org
Subject: Re: Question about your git habits
Date: Sat, 23 Feb 2008 11:39:23 +0100 [thread overview]
Message-ID: <2008-02-23-11-39-23+trackit+sam@rfc1149.net> (raw)
In-Reply-To: <7vk5kw4fep.fsf@gitster.siamese.dyndns.org> (Junio C. Hamano's message of "Fri\, 22 Feb 2008 17\:42\:22 -0800")
>>>>> "Junio" == Junio C Hamano <gitster@pobox.com> writes:
Junio> Many people prefer to use topic branches, and working in a
Junio> single repository with multiple branches and switching branches
Junio> without ever cd'ing around is certainly a possible and very
Junio> valid way to work. As long as your build infrastructure is
Junio> sane (e.g. your project does not have a central header file
Junio> that any little subsystem change needs to modify and included
Junio> by everybody, which tends to screw up make quite badly),
Junio> switching branches would not incur too much recompilation
Junio> either and it obviously will save disk space not having to
Junio> leave multiple checkout around.
And even in this case (central header file), ccache will greatly
decrease compilation time in the case of a C/C++ project.
Sam
--
Samuel Tardieu -- sam@rfc1149.net -- http://www.rfc1149.net/
next prev parent reply other threads:[~2008-02-23 10:51 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 [this message]
[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
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=2008-02-23-11-39-23+trackit+sam@rfc1149.net \
--to=sam@rfc1149.net \
--cc=chase.venters@clientec.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).