From: Linus Torvalds <torvalds@linux-foundation.org>
To: Matthew L Foster <mfoster167@yahoo.com>
Cc: git@vger.kernel.org, david@lang.hm
Subject: Re: merge time
Date: Sun, 29 Jul 2007 20:09:01 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707292007440.4161@woody.linux-foundation.org> (raw)
In-Reply-To: <686661.84825.qm@web51011.mail.re2.yahoo.com>
On Sun, 29 Jul 2007, Matthew L Foster wrote:
>
> > but if git did what you wanted it would show every commit with the time of
> > the merge, and that wouldn't help you anyway.
>
> Actually that is exactly what I want. I want to know what local time change X and Y (and all
> changes) were merged locally.
You misunderstand. It would do so both for the newly merged commits *and*
for the old commits. Because _you_ think the "new" commits got merged, but
it's logically exactly equivalent to saying that the *old* commits got
merged.
So now *every* single commit would get the timestamp of the merge.
See? It would be pointless.
Linus
next prev parent reply other threads:[~2007-07-30 3:09 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 2:28 merge time Matthew L Foster
2007-07-30 3:09 ` Linus Torvalds [this message]
2007-07-30 4:10 ` Matthew L Foster
2007-07-30 4:17 ` david
2007-07-30 16:20 ` Matthew L Foster
2007-07-30 16:23 ` david
2007-07-30 17:11 ` Matthew L Foster
2007-07-30 17:33 ` david
2007-07-30 22:11 ` Robin Rosenberg
-- strict thread matches above, loose matches on Subject: below --
2007-07-29 17:33 Matthew L Foster
2007-07-29 23:19 ` Jakub Narebski
2007-07-29 23:35 ` Linus Torvalds
2007-07-30 1:11 ` Matthew L Foster
2007-07-30 1:27 ` david
2007-07-30 2:29 ` Linus Torvalds
2007-07-30 2:43 ` Matthew L Foster
2007-07-30 3:06 ` Linus Torvalds
2007-07-30 3:16 ` Linus Torvalds
2007-07-30 4:13 ` Matthew L Foster
2007-07-30 11:33 ` Sean
2007-07-30 3:57 ` Matthew L Foster
2007-07-30 6:10 ` Steffen Prohaska
2007-07-30 6:48 ` Junio C Hamano
2007-07-30 7:44 ` Steffen Prohaska
2007-07-30 7:49 ` Shawn O. Pearce
2007-07-30 8:09 ` Steffen Prohaska
2007-07-30 8:14 ` Jeff King
2007-07-30 8:24 ` Junio C Hamano
2007-07-30 8:31 ` Jeff King
2007-07-30 8:25 ` Steffen Prohaska
2007-07-30 8:32 ` Jeff King
2007-07-30 8:34 ` david
2007-07-30 8:41 ` Jeff King
2007-07-30 17:42 ` Linus Torvalds
2007-07-31 18:06 ` Steffen Prohaska
2007-07-31 20:07 ` david
2007-07-30 12:44 ` Rogan Dawes
2007-07-30 16:14 ` Matthew L Foster
2007-07-30 16:20 ` Johannes Schindelin
2007-07-30 16:24 ` Matthew L Foster
2007-07-30 16:25 ` Rogan Dawes
2007-07-30 17:06 ` Matthew L Foster
2007-07-30 17:13 ` david
2007-07-30 21:57 ` 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=alpine.LFD.0.999.0707292007440.4161@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=david@lang.hm \
--cc=git@vger.kernel.org \
--cc=mfoster167@yahoo.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).