From: Ryan Anderson <ryan@michonline.com>
To: Andrea Arcangeli <andrea@cpushare.com>
Cc: dtor_core@ameritech.net, linux-kernel@vger.kernel.org,
klive@cpushare.com, Ian Wienand <ianw@gelato.unsw.edu.au>,
Sam Ravnborg <sam@ravnborg.org>
Subject: Re: git tag in localversion
Date: Tue, 13 Sep 2005 04:31:27 -0400 [thread overview]
Message-ID: <20050913083120.GG5276@mythryan2.michonline.com> (raw)
In-Reply-To: <20050912222137.GP13439@opteron.random>
On Tue, Sep 13, 2005 at 12:21:37AM +0200, Andrea Arcangeli wrote:
> On Mon, Sep 12, 2005 at 04:31:24PM -0500, Dmitry Torokhov wrote:
> > I think this question better be addressed to Ian or Sam (Andrea, did
> > you pick a wrong entry from your address book?), adding them to CC...
>
> hmm, if you're not the right person it means hg log -p has some
> problem... this changeset was submitted by you according to mercurial.
I submitted the "Auto Localversion" change (and a fix for the fact that
it doesn't auto-disappear on a tagged version like it is supposed to,
submitted 5 minutes ago).
Yes, the goal of this was to avoid overwriting similar, but different
versions, for those of us who are, too lazy to download patches,
but are willing to type "git pull origin && make oldconfig && make" on a
regular basis.
My suggestion would be to classify these wherever they would fall if the
-gXXXXXXXX wasn't present, as they fall into the same category.
They won't get as much testing, but if you see 5 or 10 of these in the
same category and -rc range, that's a good indication that a few people
are testing those kernels.
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2005-09-13 8:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 21:08 Andrea Arcangeli
2005-09-12 21:31 ` Dmitry Torokhov
2005-09-12 22:21 ` Andrea Arcangeli
2005-09-12 23:25 ` Dmitry Torokhov
2005-09-13 8:31 ` Ryan Anderson [this message]
2005-09-13 14:16 ` Andrea Arcangeli
2005-09-15 1:56 ` Andrea Arcangeli
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=20050913083120.GG5276@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=andrea@cpushare.com \
--cc=dtor_core@ameritech.net \
--cc=ianw@gelato.unsw.edu.au \
--cc=klive@cpushare.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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
all inboxes | Powered by JetHome®