From: Dave Jones <davej@redhat.com>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: linux-kernel@vger.kernel.org, Maneesh Soni <maneesh@in.ibm.com>
Subject: Re: Can we please keep correct date when doing bk checkins?
Date: Mon, 14 Jun 2004 20:34:15 +0100 [thread overview]
Message-ID: <20040614193415.GA28002@redhat.com> (raw)
In-Reply-To: <20040614184523.93825.qmail@web81301.mail.yahoo.com>
On Mon, Jun 14, 2004 at 11:45:23AM -0700, Dmitry Torokhov wrote:
> I noticed that while the sysfs_rename_dir-cleanup changeset was checked
> in on May 14, 2004 dathes on the touched files read 2004/10/06 which is
> obviously incorrect.
What makes you think this is incorrect ?
It's possible whoever checked in that change did it in their repo
on May 14th, and then Linus pulled the change into his tree on the
10th June, which would alter the timestamp.
Dave
next prev parent reply other threads:[~2004-06-14 19:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 18:45 Can we please keep correct date when doing bk checkins? Dmitry Torokhov
2004-06-14 19:34 ` Dave Jones [this message]
2004-06-14 19:36 ` Maneesh Soni
2004-06-14 19:34 ` Maneesh Soni
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=20040614193415.GA28002@redhat.com \
--to=davej@redhat.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.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