From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] SVN/trac requests
Date: Tue, 26 Sep 2006 16:56:35 +0000 [thread overview]
Message-ID: <20060926185635.ffc78804.khali@linux-fr.org> (raw)
In-Reply-To: <20060926140502.00d29dd5.khali@linux-fr.org>
> Hi,
>
> On Tue, Sep 26, 2006 at 02:05:02PM +0200, Jean Delvare wrote:
> > I have the two following requests with regards to lm-sensors' SVN/trac:
> >
> > 1* Can the "V-2-3-1" tag be renamed to "V2-3-1"?
>
> Yes, the contents of "tags" is (for svn) just another folder, so just
> as you rename conventional files/folders under svn you ranme this one,
> too, e.g. "svn mv V-2-3-1 V2-3-1; svn ci ." in the tags folder should
> be enough.
Yeah, it worked :) Thanks! I expected something more obscure. In fact I
didn't expect it to be possible from the client side. Now the only
drawback is that the timestamp on the renamed directory changed, but
that's a minor annoyance we should be able to live with.
> > 2* We often need to ask people to try the latest version of
> > sensors-detect. For now we point them to:
> > http://www.lm-sensors.org/browser/lm-sensors/trunk/prog/detect/sensors-detect?format=txt
> >
> > The problem is that this version of the SVN file doesn't have its
> > keywords substituted, so the version string reads:
> > '$Revision$ ($Date$)'
> > This might become a problem in the long run when users report with this
> > version string, as we will be unable to tell what version of the file
> > they have. So, is it possible to ask trac to provide the file with
> > keywords substituted? I'm surprised this isn't the default...
>
> 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
Then this is considered an external link by trac, which adds a special
icon in front of it. I linked to trac to avoid that.
> 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. :(
I guessed so, but trac could be seen as a client.
--
Jean Delvare
next prev parent reply other threads:[~2006-09-26 16:56 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 [this message]
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
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=20060926185635.ffc78804.khali@linux-fr.org \
--to=khali@linux-fr.org \
--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.