From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: "Ulrich Windl" <ulrich.windl@rz.uni-regensburg.de>
Cc: Dmitry Potapov <dpotapov@gmail.com>, git@vger.kernel.org
Subject: Re: On git 1.6 (novice's opinion)
Date: Fri, 27 Mar 2009 14:44:13 +0100 [thread overview]
Message-ID: <vpq63hvdqs2.fsf@bauges.imag.fr> (raw)
In-Reply-To: <49CCE421.16918.2582FE84@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de> (Ulrich Windl's message of "Fri\, 27 Mar 2009 14\:35\:13 +0100")
"Ulrich Windl" <ulrich.windl@rz.uni-regensburg.de> writes:
> I don't understand:
> If I modify files, then do a make, then do check-in/check-out (and the file times
> are unchanged), how would that affect make?
>From "make"'s point of view, chechout is just a modification of the
file (as any other modification you would do with a text editor). If
you compile foo.c to foo.o, then checkout another version of foo.c,
then you want foo.c to be recompiled. If checkout modifies the
timestamp to pretend it was modified before foo.o, then make thinks
the file is up to date.
> If I do an "update/merge from remote" (there is no total ordering of release
> numbers anyway) without a "make clean" before, I'm having a problem
> anyway.
No, you don't have a problem. Recompiling files after they're modified
is the job of make, and it just does it. make doesn't know about
revision numbers or identifiers, just timestamps.
--
Matthieu
next prev parent reply other threads:[~2009-03-27 13:49 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-27 7:21 On git 1.6 (novice's opinion) Ulrich Windl
2009-03-27 8:05 ` H.Merijn Brand
2009-03-27 9:50 ` Ulrich Windl
2009-03-27 10:57 ` Etienne Vallette d'Osia
2009-03-27 11:30 ` Etienne Vallette d'Osia
2009-03-27 12:24 ` Dmitry Potapov
2009-03-27 13:39 ` Ulrich Windl
2009-03-27 13:45 ` Matthieu Moy
2009-03-27 13:47 ` Etienne Vallette d'Osia
2009-04-01 6:50 ` Ulrich Windl
2009-04-01 7:41 ` Matthieu Moy
2009-03-28 1:30 ` Junio C Hamano
2009-03-28 1:30 ` Junio C Hamano
2009-03-28 9:53 ` Dmitry Potapov
2009-03-30 6:18 ` Russ Dill
2009-04-01 7:53 ` Ulrich Windl
2009-04-01 8:37 ` Andreas Ericsson
2009-04-01 9:47 ` Ulrich Windl
2009-04-01 10:17 ` Andreas Ericsson
2009-04-01 20:37 ` Heiko Voigt
2009-03-27 12:24 ` Dmitry Potapov
2009-03-27 13:35 ` Ulrich Windl
2009-03-27 13:44 ` Matthieu Moy [this message]
2009-04-01 6:45 ` Ulrich Windl
2009-04-01 7:42 ` Matthieu Moy
2009-03-27 12:49 ` Michael J Gruber
2009-03-27 13:48 ` Ulrich Windl
2009-03-27 14:09 ` Jakub Narebski
2009-04-01 6:59 ` Ulrich Windl
2009-04-01 7:29 ` Andreas Ericsson
2009-04-01 7:54 ` Matthieu Moy
2009-04-01 9:38 ` Ulrich Windl
2009-04-01 10:10 ` Andreas Ericsson
2009-04-02 2:17 ` Jakub Narebski
2009-03-28 10:33 ` demerphq
2009-03-28 1:30 ` Junio C Hamano
2009-04-01 7:35 ` Ulrich Windl
2009-03-29 5:41 ` Bryan Donlan
2009-03-29 9:50 ` Johannes Schindelin
2009-04-01 7:42 ` Ulrich Windl
2009-04-01 7:40 ` Ulrich Windl
2009-03-30 9:06 ` Andreas Ericsson
2009-04-01 8:15 ` Ulrich Windl
2009-04-01 8:41 ` Andreas Ericsson
2009-04-01 9:55 ` Ulrich Windl
2009-04-01 10:21 ` Andreas Ericsson
2009-04-01 11:52 ` Ulrich Windl
2009-04-01 12:40 ` Andreas Ericsson
2009-04-01 2:32 ` Kris Shannon
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=vpq63hvdqs2.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=dpotapov@gmail.com \
--cc=git@vger.kernel.org \
--cc=ulrich.windl@rz.uni-regensburg.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.