From: Axel Thimm <Axel.Thimm@ATrpms.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Branches in lm-sensors repository
Date: Mon, 26 Jan 2009 17:48:23 +0000 [thread overview]
Message-ID: <20090126174823.GE10884@victor.nirvana> (raw)
In-Reply-To: <20090119222636.0380a479@hyperion.delvare>
[-- Attachment #1.1: Type: text/plain, Size: 877 bytes --]
Hi,
On Mon, Jan 26, 2009 at 06:36:46PM +0100, Jean Delvare wrote:
> > It leaves the question of where the snapshots go to now. Previously
> > the 3.x snapshots went under /lm-sensors-3/snapshots/, I guess they
> > would now better show up under /lm-sensors/snapshots/?
>
> Yes. But I don't think you need to do anything special for this:
> snapshots of trunk already went into /lm-sensors/snapshots/, and the
> development branch is now trunk again. So the old command should
> already do the right thing.
True, so it just needed removing the cron job for lm-sensors-3. Well
planned when you set this up ;)
> > Should we remove /lm-sensors-3/ altogether?
>
> Yes, please.
OK, done. Should all work as you said, but maybe we should check the
contents of the next snapshot tomorrow (runs at 6:10 CET) just to make
sure.
--
Axel.Thimm at ATrpms.net
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-01-26 17:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 21:26 [lm-sensors] Branches in lm-sensors repository Jean Delvare
2009-01-26 15:51 ` Jean Delvare
2009-01-26 16:58 ` Jean Delvare
2009-01-26 17:27 ` Axel Thimm
2009-01-26 17:36 ` Jean Delvare
2009-01-26 17:48 ` Axel Thimm [this message]
2009-01-27 8:48 ` Jean Delvare
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=20090126174823.GE10884@victor.nirvana \
--to=axel.thimm@atrpms.net \
--cc=lm-sensors@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.