linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Hin-Tak Leung <hintak.leung@gmail.com>
Cc: "P.G. Richardson" <p.g.richardson@phantomjinx.co.uk>,
	Larry Finger <Larry.Finger@lwfinger.net>,
	linux-wireless@vger.kernel.org
Subject: Re: rtl8187 wireless issues
Date: Tue, 3 Feb 2009 09:28:07 -0500	[thread overview]
Message-ID: <20090203142807.GC10968@tuxdriver.com> (raw)
In-Reply-To: <3ace41890902021548o39b5f02veacc0bd650e92c7@mail.gmail.com>

On Mon, Feb 02, 2009 at 11:48:55PM +0000, Hin-Tak Leung wrote:

> About dates in wireless-testing log - I had an impression (I could be
> wrong) that the dates are sometimes git-format-patch/posting dates and
> not dates at which John commits to wireless-testing? (i.e. the dates
> shown could be a lot earlier than time of commit, or time of commit is
> not shown by the dates associated with a patch - I thought this makes
> sense since the date of a patch should be the first time it appears in
> the "system", not the first time it gets in-coporated in a particular
> tree, and patches can go between trees and should *not* pick up date
> change on the way).

Patch dates in 'git log' are based on their reported creation time or
(for patches not from git) their posting time.  That's just the way
git works (at least by default).

I generally tag wireless-testing updates on the master branch with
a date-based tag.  You can see them like this:

	git fetch --tags # just in case...
	git tag | grep master

Hth!

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-02-03 14:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29 12:46 rtl8187 wireless issues P.G. Richardson
2009-01-29 17:52 ` Hin-Tak Leung
2009-01-30 13:59   ` P.G. Richardson
2009-01-30 19:17     ` Hin-Tak Leung
2009-01-30 22:04       ` P.G. Richardson
2009-02-02  1:09         ` Hin-Tak Leung
2009-02-02 13:51           ` P.G. Richardson
2009-02-02 15:25             ` Larry Finger
2009-02-02 15:56               ` P.G. Richardson
2009-02-02 23:48                 ` Hin-Tak Leung
2009-02-03 14:28                   ` John W. Linville [this message]
2009-02-03 16:39                     ` P.G. Richardson
2009-02-03 17:04                       ` Larry Finger
2009-02-05 20:18                         ` rtl8187 sleeping/hanging P.G. Richardson
2009-02-05 21:38                           ` Larry Finger
2009-02-05 23:01                             ` P.G. Richardson
2009-02-06 17:47                               ` Larry Finger
2009-02-06 18:56                                 ` P.G. Richardson

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=20090203142807.GC10968@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=hintak.leung@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=p.g.richardson@phantomjinx.co.uk \
    /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).