All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel.Thimm@ATrpms.net (Axel Thimm)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] SVN/trac requests
Date: Tue, 26 Sep 2006 19:32:35 +0000	[thread overview]
Message-ID: <20060926193235.GP10410@neu.nirvana> (raw)
In-Reply-To: <20060926140502.00d29dd5.khali@linux-fr.org>

Hi,

On Tue, Sep 26, 2006 at 09:23:00PM +0200, Jean Delvare wrote:
> > On Tue, Sep 26, 2006 at 07:10:22PM +0200, Jean Delvare wrote:
> > > > Axel Thimm wrote:
> > > >   > Hm, I don't have a solution. First of all I wouldn't loop it through
> > > > > trac, but use the direct svn URL instead, e.g.
> > > > > 
> > > > > http://lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect
> > > > > 
> > > > > But this has the same issue, so it doesn't solve the issue at hand.
> > > > > 
> > > > > I would guess that the keyword substitution happens at the client, and
> > > > > svn/trac offer the raw contents only. :(
> > 
> > > Another option is to give the users a simple svn command to type to
> > > retrieve just that file:
> > >   svn export http://lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect
> > > 
> > > However it is significantly less convenient, as the user might not have
> > > svn installed. Or maybe we can install a simple CGI script on the web
> > > server which would run this command and return the result to the
> > > user? I can't seem to find an option to output the file to stdout
> > > though, which we would need.
> > 
> > If no native solution in svn/trac is found maybe the scripts doing the
> > snapshots could extract this file w/ keywords and place it to a
> > canonical place?
> 
> This would imply up to 24h of delay before the user can pick the new
> version of the script. I'm OK with daily snapshots for the project
> itself, but sensors-detect is a bit special in that it helps us
> investigating user problems, and being able to update the script with
> new data and tell the user to try the new version the minute after is
> very convenient.

Indeed, stretching feedback cycles to 24 hours is ugly. :/

> I wouldn't bother if the script wasn't run by root. I'd make the file
> available on my server and I'd tell the users to pick it there. But
> from a security point of view, that sucks. I really want people to get
> a file from lm-sensors.org. And I want the file to come right out of
> the Subversion repository, with no man in the middle.

Still assuming there is no native way to ask trac/svn to add keyword
expansion, live cuts could be made by using svn's commit triggering
system instead of using cron.
-- 
Axel.Thimm at ATrpms.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060926/a629e43e/attachment.bin 

  parent reply	other threads:[~2006-09-26 19:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-26 12:05 [lm-sensors] SVN/trac requests Jean Delvare
2006-09-26 13:53 ` Axel Thimm
2006-09-26 15:43 ` Michael Renzmann
2006-09-26 16:56 ` Jean Delvare
2006-09-26 17:10 ` Jean Delvare
2006-09-26 17:16 ` Jean Delvare
2006-09-26 18:27 ` Axel Thimm
2006-09-26 18:40 ` Axel Thimm
2006-09-26 19:23 ` Jean Delvare
2006-09-26 19:32 ` Axel Thimm [this message]
2006-09-27  2:33 ` Michael Renzmann
2006-09-27  2:56 ` Michael Renzmann
2006-09-27  7:32 ` 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=20060926193235.GP10410@neu.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.