From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Bill Lear" <rael@zopyra.com>
Cc: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Karl Hasselström" <kha@treskal.com>,
git@vger.kernel.org
Subject: Re: Git checkout preserve timestamp?
Date: Tue, 6 Mar 2007 13:06:21 +1300 [thread overview]
Message-ID: <46a038f90703051606m7ce73f88hd0f6356969b73535@mail.gmail.com> (raw)
In-Reply-To: <17900.43487.947400.649777@lisa.zopyra.com>
On 3/6/07, Bill Lear <rael@zopyra.com> wrote:
> No, I think you missed my point. There are two xyz.o's:
>
> One in .master/xyz.o, and one in .branchX/xyz.o. So, you're example
> becomes:
For most users, there are no dedicated branch-specific build
directories. In any situation where there _are_ such
branch/arch/config-option specific builddirs, someone has crafted a
neat multi-<factor> build system.
Now, if you have such a build system, it's trivial to have a separate
checkout for each branch. Trying to push this bit of complexity into
git means that git would have an option that lets most users shoot
themselves in the foot, big time.
So - your ideas are OK, but just do all the trickery and magic for the
super-build-system _in_ the super-build-system. You don't need any GIT
changes, just take advantage of the really fast and lightweight "local
clone".
I guess that's the definition of "WRONG" above. It's wrong and
error-prone for most users, and for the handsome few that could take
advantage of it, there are better ways of doing it.
cheers,
martin
next prev parent reply other threads:[~2007-03-06 0:06 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 21:36 Git checkout preserve timestamp? Bill Lear
2007-03-01 21:48 ` Alex Riesen
2007-03-01 22:13 ` Johannes Schindelin
2007-03-01 22:25 ` Linus Torvalds
2007-03-01 22:32 ` Johannes Schindelin
2007-03-02 9:14 ` Karl Hasselström
2007-03-02 13:24 ` Bill Lear
2007-03-02 15:01 ` Bart Trojanowski
2007-03-02 15:18 ` Johannes Schindelin
2007-03-02 16:21 ` Karl Hasselström
2007-03-02 19:21 ` Johannes Schindelin
2007-03-05 7:23 ` Karl Hasselström
2007-03-05 11:32 ` Johannes Schindelin
2007-03-05 12:28 ` Karl Hasselström
2007-03-05 19:04 ` Bill Lear
2007-03-05 19:16 ` Johannes Schindelin
2007-03-05 19:59 ` Bill Lear
2007-03-05 20:44 ` Johannes Schindelin
2007-03-05 21:42 ` Bill Lear
2007-03-05 21:50 ` Linus Torvalds
2007-03-05 22:03 ` Matthieu Moy
2007-03-05 22:25 ` Bill Lear
2007-03-05 22:37 ` Linus Torvalds
2007-03-05 23:20 ` Bill Lear
2007-03-05 23:32 ` Johannes Schindelin
2007-03-05 23:38 ` Bill Lear
2007-03-05 23:50 ` Johannes Schindelin
2007-03-06 0:06 ` Michael Poole
2007-03-06 0:20 ` Johannes Schindelin
2007-03-06 0:37 ` Michael Poole
2007-03-06 1:40 ` Johannes Schindelin
2007-03-06 0:32 ` Junio C Hamano
2007-03-06 18:39 ` Sergio Callegari
[not found] ` <7vo dn7w6rz.fsf@assigned-by-dhcp.cox.net>
2007-03-06 1:21 ` Jakub Narebski
2007-03-06 0:24 ` Bill Lear
2007-03-06 1:34 ` Johannes Schindelin
2007-03-06 1:59 ` Bill Lear
2007-03-06 0:06 ` Martin Langhoff [this message]
2007-03-06 0:21 ` Theodore Tso
2007-03-05 22:39 ` Matthieu Moy
2007-03-05 22:56 ` Johannes Schindelin
2007-03-05 23:27 ` Bill Lear
2007-03-05 22:02 ` Johannes Schindelin
2007-03-05 22:29 ` Bill Lear
2007-03-05 12:13 ` Andy Parkins
2007-03-05 12:33 ` Karl Hasselström
2007-03-05 13:19 ` Andy Parkins
2007-03-05 14:53 ` Karl Hasselström
2007-03-05 14:46 ` Bill Lear
2007-03-05 16:01 ` Andy Parkins
2007-03-05 16:28 ` Bill Lear
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=46a038f90703051606m7ce73f88hd0f6356969b73535@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=rael@zopyra.com \
--cc=torvalds@linux-foundation.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).