From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Kernel nightly snapshots..
Date: Fri, 06 May 2005 08:42:23 +0100 [thread overview]
Message-ID: <1115365344.29495.37.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0505050834550.2328@ppc970.osdl.org>
On Thu, 2005-05-05 at 08:46 -0700, Linus Torvalds wrote:
> So this _should_ work for a while, but will eventually (before a -rc10
> happens or we get to v2.6.100 ;^) need something better. That something
> better probably being to ignore any tags that don't point to commits, and
> then sorting by the date of the commit object.
Enough with the dates already. I don't want to be doing snapshots
against 2.6.11.9 just because that happened to get tagged more recently
than 2.6.12-rc4. Time is an illusion; especially so when looking at
branches which may not even have been merged.
The tag I want is the one which refers to a commit which is made by
yourself and is accessible from the current HEAD in the lowest number of
steps. And I don't _care_ if you tagged it 'Woozy Numbat'.
--
dwmw2
prev parent reply other threads:[~2005-05-06 7:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 0:28 Kernel nightly snapshots Linus Torvalds
2005-05-05 2:06 ` H. Peter Anvin
2005-05-05 14:38 ` David Woodhouse
2005-05-05 14:44 ` Linus Torvalds
2005-05-05 15:10 ` David Woodhouse
2005-05-05 15:30 ` David Woodhouse
2005-05-05 16:40 ` Linus Torvalds
2005-05-07 12:39 ` David Woodhouse
2005-05-06 0:28 ` H. Peter Anvin
2005-05-06 7:29 ` David Woodhouse
2005-05-06 21:50 ` H. Peter Anvin
2005-05-06 21:51 ` Marcelo Tosatti
2005-05-22 11:50 ` Thomas Glanzmann
2005-05-22 11:59 ` David Woodhouse
2005-05-22 12:09 ` Thomas Glanzmann
2005-05-22 17:01 ` Russell King
2005-05-05 15:46 ` Linus Torvalds
2005-05-06 7:42 ` David Woodhouse [this message]
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=1115365344.29495.37.camel@localhost.localdomain \
--to=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=torvalds@osdl.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).