You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by "Martin@Cleaver.org" <Ma...@Cleaver.org> on 2008/08/06 19:43:24 UTC
A wiki for this group
On Wed, Aug 6, 2008 at 2:24 PM, Ryan Schmidt <
subversion-2008c@ryandesign.com> wrote:
> On Aug 5, 2008, at 22:03, Martin@Cleaver.org wrote:
>
>> (How about using a wiki instead of the mailing list? I found the svn
>> vendor branch documentation just terrible for a newbie)
>>
> A wiki is not a substitute for a mailing list. A mailing list is for
> questions and answers, and for troubleshooting. A wiki is for documentation.
>
Ok. So keep the mailing list. Would the community benefit from a wiki for
documentation as well?
For those people not on the mailing list, who aren't in the conversation day
in day out, and who want a reference source a wiki could be really useful...
(and a wiki set up to file all email can be even more useful).
Re: A wiki for this group
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Aug 6, 2008, at 21:55, Martin@Cleaver.org wrote:
> I just checked and it is the most authoritative, doing well on
> Google at #9 on http://www.google.ca/search?num=100q=subversion
> +wiki and #4 on http://www.google.ca/search?q=svn+wiki ... funnily
> enough I didn't search that way. I was navigating...
>
> As I would like it's content to be considered *the* wiki I just
> added it to the /topic on #svn on irc.freenode.net: that will give
> it some airing. Ideally it would need to feature on navigation from
> tigris.org: so who do we lobby to make that happen? Is there any
> factor (such as the name) that would make it more obvious to users
> what it is about?
>
> As for svn_load_dirs.pl, it certainly does a good job as far as it
> goes. I'd just like it to go further, and in particular with
> respect to how it handles renames.
I think you can just check out the www part of the Subversion
repository, make your changes, and submit the output of "svn di" as a
patch.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: A wiki for this group
Posted by "Martin@Cleaver.org" <Ma...@Cleaver.org>.
Hi, Thanks Blair. Glad to see there is *a* wiki.
I just checked and it is the most authoritative, doing well on Google at #9
on http://www.google.ca/search?num=100q=subversion+wiki and #4 on
http://www.google.ca/search?q=svn+wiki ... funnily enough I didn't search
that way. I was navigating...
As I would like it's content to be considered *the* wiki I just added it to
the /topic on #svn on irc.freenode.net: that will give it some airing.
Ideally it would need to feature on navigation from tigris.org: so who do we
lobby to make that happen? Is there any factor (such as the name) that
would make it more obvious to users what it is about?
As for svn_load_dirs.pl, it certainly does a good job as far as it goes. I'd
just like it to go further, and in particular with respect to how it handles
renames.
M..
--
Martin@Cleaver.org
+1 416-786-6752 (GMT-5)
On Wed, Aug 6, 2008 at 7:39 PM, Blair Zajac <bl...@orcaware.com> wrote:
> Martin@Cleaver.org wrote:
>
>> On Wed, Aug 6, 2008 at 2:24 PM, Ryan Schmidt <
>> subversion-2008c@ryandesign.com <ma...@ryandesign.com>>
>> wrote:
>>
>> On Aug 5, 2008, at 22:03, Martin@Cleaver.org wrote:
>>
>> (How about using a wiki instead of the mailing list? I found the
>> svn vendor branch documentation just terrible for a newbie)
>>
>> A wiki is not a substitute for a mailing list. A mailing list is for
>> questions and answers, and for troubleshooting. A wiki is for
>> documentation.
>>
>>
>> Ok. So keep the mailing list. Would the community benefit from a wiki for
>> documentation as well?
>>
>
> Hi Martin,
>
> There is a wiki I host at
>
> http://www.orcaware.com/svn/wiki/Main_Page
>
> Feel free to contribute to it.
>
> BTW, I wrote svn_load_dirs.pl way back in 2002 when there was nothing else
> available to import vendor drops into svn. Feel free to criticize it, I
> won't take it personally, it did a great job when it was first written way
> back in svn 1.0 times :)
>
> Regards,
> Blair
>
Re: A wiki for this group
Posted by Blair Zajac <bl...@orcaware.com>.
Martin@Cleaver.org wrote:
> On Wed, Aug 6, 2008 at 2:24 PM, Ryan Schmidt
> <subversion-2008c@ryandesign.com
> <ma...@ryandesign.com>> wrote:
>
> On Aug 5, 2008, at 22:03, Martin@Cleaver.org wrote:
>
> (How about using a wiki instead of the mailing list? I found the
> svn vendor branch documentation just terrible for a newbie)
>
> A wiki is not a substitute for a mailing list. A mailing list is for
> questions and answers, and for troubleshooting. A wiki is for
> documentation.
>
>
> Ok. So keep the mailing list. Would the community benefit from a wiki
> for documentation as well?
Hi Martin,
There is a wiki I host at
http://www.orcaware.com/svn/wiki/Main_Page
Feel free to contribute to it.
BTW, I wrote svn_load_dirs.pl way back in 2002 when there was nothing else
available to import vendor drops into svn. Feel free to criticize it, I won't
take it personally, it did a great job when it was first written way back in svn
1.0 times :)
Regards,
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: A wiki for this group
Posted by "Martin@Cleaver.org" <Ma...@Cleaver.org>.
What it is that makes this like a wiki to you?
I'm supposing you have seen contributions emailed into the authors being
incorporated?
Until one puts the edit controls and the editorial process into an open
collaborative process, I'd position that its not sufficiently wiki-like.
It's a one-webmaster scenario. That the book authors are so good at
incorporating public contributions doesn't make the same wiki like promises
to would be contributors. In particular it doesn't promise inclusion and
doesn't help people collectively figure out what is relevant.
Sure the process may work (I assume it does), but I imagine that newcomers
can't see the effectiveness of the process you have. The public are
understanding the promise of a well-maintained wiki. Seeing that promise in
itself is more likely to get contributions.
It would be an interesting experiment to front your existing process with a
wiki. Instead of taking contributions by email take them through the wiki.
Regards,
Martin.
--
Martin@Cleaver.org
+1 416-786-6752 (GMT-5)
On Wed, Aug 6, 2008 at 4:24 PM, Johnathan Gifford <jg...@wernervas.com>wrote:
> We have a wiki! You can find it at:
>
> http://svnbook.red-bean.com/
>
> If you don't like something in the book, then contribute to the book.
>
> Johnathan
>
> >>> On Wed, Aug 6, 2008 at 2:43 PM, in message
> <fe...@mail.gmail.com>,
> "Martin@Cleaver.org" <Ma...@Cleaver.org> wrote:
> > On Wed, Aug 6, 2008 at 2:24 PM, Ryan Schmidt <
> > subversion-2008c@ryandesign.com> wrote:
> >
> >> On Aug 5, 2008, at 22:03, Martin@Cleaver.org wrote:
> >>
> >>> (How about using a wiki instead of the mailing list? I found the svn
> >>> vendor branch documentation just terrible for a newbie)
> >>>
> >> A wiki is not a substitute for a mailing list. A mailing list is for
> >> questions and answers, and for troubleshooting. A wiki is for
> documentation.
> >>
> >
> > Ok. So keep the mailing list. Would the community benefit from a wiki for
> > documentation as well?
> >
> > For those people not on the mailing list, who aren't in the conversation
> day
> > in day out, and who want a reference source a wiki could be really
> useful...
> > (and a wiki set up to file all email can be even more useful).
> >
> > From http://subversion.tigris.org/tools_contrib.html search for the word
> > "vendor" - nothing. You'd need to look for svn_load_dirs.pl (which is an
> > obscure name, relative to "vendor branch"); From Blair's email I now know
> > that there is a tool "piston" that manages Subversion Vendor Branches,
> but
> > there's no "vendor branch" category and no other tools category "import",
> > and indeed, "piston" doesn't exist anywhere on this page. Even searching
> for
> > "rename" on this page yields no hits. Sure I could have sent an email,
> and
> > waited 24 hours. But I did ask on #svn and they pointed me back at
> > svn_load_dirs.pl, which after a lot of head scratching I worked out how
> to
> > use and build a tool to harness, only to find that it's impractical
> because
> > of the renaming issues.
> >
> > The existing site is somewhat broken. For instance from
> > http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=121964I
> > click "Contributed tools" and get taken to the 404 at
> > http://subversion.tigris.org/servlets/tools_contrib.html ; if the site
> was a
> > wiki more people could help to maintain the site structure.
> >
> > For instance, a wiki would have a page called SVN Vendor Branches that
> > collected the best ways of describing what one is and which tools can
> manage
> > them.
> >
> > A wiki is not a substitute for a book either. A book is written and
> reviewed
> > by editors and formatted carefully and organized and changes are
> considered
> > before being accepted. Wikis accept all changes, some of which should
> never
> > have been accepted, or should have been in different places, or do not
> match
> > the style of the rest of the document. Especially in the case of the
> > Subversion book, I wouldn't change its process. I find it excellent.
> >
> >
> > Yup, the book like the old timers on the mailing list is written by
> people
> > who understand the concept. Wikis are open to newcomers who will inform
> you
> > of what they didn't understand and help experts frame complex ideas in
> > simple langauage.
> >
> > I simply didn't understand the chapter on vendor branches, and neither
> did
> > these people:
> >
> > "I use Subversion and a concept called 'vendor branches.' Sadly, their
> > documentation is confusing " -
> > http://lookfirst.com/2007/11/subversion-vendor-branches-howto.html
> >
> > "I read the Subversion book, which confused me a bit and pointed me
> towards
> > svn_load_dirs, which has both a man page and a README, neither of which
> make
> > a great deal of sense. " -
> > http://burtonini.com/blog/computers/svn-vendor-2005-05-04-13-55
> >
> > "I found the vendor branch concept a bit confusing;" -
> >
> http://techlog.p2061.org/2008/05/21/using-svn-for-application-deployment/
> >
> >
> >
> > That's not to say it can't be improved in places. The writers welcome
> > feedback. You should send it to the book mailing list. Info about how to
> do
> > that is near the bottom of http://svnbook.org/ .
> >
> >
> > If it was a wiki I'd contribute. Indeed, probably the people who wrote
> those
> > blog posts would contribute.
> >
> > A wiki is not a substitute for a book either. A book is written and
> reviewed
> >> by editors and formatted carefully and organized and changes are
> considered
> >> before being accepted. Wikis accept all changes, some of which should
> never
> >> have been accepted, or should have been in different places, or do not
> match
> >> the style of the rest of the document. Especially in the case of the
> >> Subversion book, I wouldn't change its process. I find it excellent.
> >>
> >
> > The three bloggers plus myself would likely have contribute to the wiki
> page
> > on Subversion Branches. How many people write the Subversion Book? A wiki
> > would not substitute the book, it would complement it, by providing raw
> > material, tools and useful distinctions.
> >
> > Just wanted to share my thoughts. I'm off to use Piston now. (Thanks
> Blair)
> >
> > Martin
> > --
> > Martin Cleaver M.Sc. MBA
> >
> > PS. Here's the script I wrote.
> >
> > cat svn_create_vendor_branch.pl
> > #! /bin/perl -w
> > use strict; # don't use this, use Piston http://piston.rubyforge.org/
> >
> > my $vendorurl="http://svn.automattic.com/wordpress-mu";
> > my $vendordroptag="1.2.3";
> >
> > my $workingarea="/tmp/build-$$";
> > mkdir $workingarea;
> > chdir $workingarea;
> >
> > my $repodir=$workingarea.'/repo';
> >
> > my $repobase="file://$repodir";
> > my $reponame="mysite.com";
> > my $repourl="$repobase/$reponame";
> >
> > my $repovendor=$repourl.'/vendor';
> > my $repowpmu=$repovendor.'/wpmu';
> > my $repomucurrent=$repowpmu.'/current';
> >
> > my $repoproject=$repourl.'/project';
> >
> > if ( ! -d $repodir ) {
> > mkdir $repodir
> > }
> >
> > chdir $repodir;
> > run ("svnadmin create $reponame");
> >
> > run ("svn mkdir $repovendor -m 'All code from others than me'");
> > run ("svn mkdir $repowpmu -m 'Code from the $vendorurl wpmu team at
> > Automattic'");
> > run ("svn mkdir $repomucurrent -m 'Dir for wpmu current revision'");
> >
> >
> > export_and_load($vendorurl, $vendordroptag);
> >
> > run ("svn cp $repomucurrent $repoproject -m 'Import of vendor branch
> > $vendorurl $vendordroptag'");
> >
> > my $testcheckout=$workingarea."/checkout";
> > mkdir $testcheckout;
> > chdir $testcheckout;
> >
> > run ("svn co $repourl");
> >
> > print "Checked out to $testcheckout\n";
> >
> > part2();
> >
> > run ("find . -type d | grep -v .svn");
> >
> > sub part2 {
> > my @vendordroptags=qw(1.2.4 1.2.4rc1 1.2.5 1.2.5a 1.3 1.3.2
> > 1.3.3 1.5-rc1 1.5.1);
> > foreach $vendordroptag (@vendordroptags) {
> > export_and_load($vendorurl, $vendordroptag);
> > }
> > }
> >
> > sub export_and_load {
> > my ($vendorurl, $vendordroptag) = @_;
> > chdir $workingarea;
> > run ("svn export $vendorurl/tags/$vendordroptag/");
> > run ("svn_load_dirs.pl $repowpmu -t wpmu-$vendordroptag current
> > ./$vendordroptag");
> > }
> >
> > sub run {
> > my ($cmd) = @_;
> > print $cmd."\n";
> > system $cmd;
> > }
>
>
Re: A wiki for this group
Posted by Chris White <ch...@gmail.com>.
On Wed, Aug 6, 2008 at 1:24 PM, Johnathan Gifford <jg...@wernervas.com>wrote:
> We have a wiki! You can find it at:
>
> http://svnbook.red-bean.com/
I didn't actually see a wiki link on here (and just to make sure I wasn't
completely blind I did a search and an HTML search). I'm sort of interested
in this myself (both learning and contributing).
>
> If you don't like something in the book, then contribute to the book.
>
> Johnathan
Best Regards,
Chris White
Re: A wiki for this group
Posted by Johnathan Gifford <jg...@wernervas.com>.
We have a wiki! You can find it at:
http://svnbook.red-bean.com/
If you don't like something in the book, then contribute to the book.
Johnathan
>>> On Wed, Aug 6, 2008 at 2:43 PM, in message
<fe...@mail.gmail.com>,
"Martin@Cleaver.org" <Ma...@Cleaver.org> wrote:
> On Wed, Aug 6, 2008 at 2:24 PM, Ryan Schmidt <
> subversion-2008c@ryandesign.com> wrote:
>
>> On Aug 5, 2008, at 22:03, Martin@Cleaver.org wrote:
>>
>>> (How about using a wiki instead of the mailing list? I found the svn
>>> vendor branch documentation just terrible for a newbie)
>>>
>> A wiki is not a substitute for a mailing list. A mailing list is for
>> questions and answers, and for troubleshooting. A wiki is for documentation.
>>
>
> Ok. So keep the mailing list. Would the community benefit from a wiki for
> documentation as well?
>
> For those people not on the mailing list, who aren't in the conversation day
> in day out, and who want a reference source a wiki could be really useful...
> (and a wiki set up to file all email can be even more useful).
>
> From http://subversion.tigris.org/tools_contrib.html search for the word
> "vendor" - nothing. You'd need to look for svn_load_dirs.pl (which is an
> obscure name, relative to "vendor branch"); From Blair's email I now know
> that there is a tool "piston" that manages Subversion Vendor Branches, but
> there's no "vendor branch" category and no other tools category "import",
> and indeed, "piston" doesn't exist anywhere on this page. Even searching for
> "rename" on this page yields no hits. Sure I could have sent an email, and
> waited 24 hours. But I did ask on #svn and they pointed me back at
> svn_load_dirs.pl, which after a lot of head scratching I worked out how to
> use and build a tool to harness, only to find that it's impractical because
> of the renaming issues.
>
> The existing site is somewhat broken. For instance from
> http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=121964 I
> click "Contributed tools" and get taken to the 404 at
> http://subversion.tigris.org/servlets/tools_contrib.html ; if the site was a
> wiki more people could help to maintain the site structure.
>
> For instance, a wiki would have a page called SVN Vendor Branches that
> collected the best ways of describing what one is and which tools can manage
> them.
>
> A wiki is not a substitute for a book either. A book is written and reviewed
> by editors and formatted carefully and organized and changes are considered
> before being accepted. Wikis accept all changes, some of which should never
> have been accepted, or should have been in different places, or do not match
> the style of the rest of the document. Especially in the case of the
> Subversion book, I wouldn't change its process. I find it excellent.
>
>
> Yup, the book like the old timers on the mailing list is written by people
> who understand the concept. Wikis are open to newcomers who will inform you
> of what they didn't understand and help experts frame complex ideas in
> simple langauage.
>
> I simply didn't understand the chapter on vendor branches, and neither did
> these people:
>
> "I use Subversion and a concept called 'vendor branches.' Sadly, their
> documentation is confusing " -
> http://lookfirst.com/2007/11/subversion-vendor-branches-howto.html
>
> "I read the Subversion book, which confused me a bit and pointed me towards
> svn_load_dirs, which has both a man page and a README, neither of which make
> a great deal of sense. " -
> http://burtonini.com/blog/computers/svn-vendor-2005-05-04-13-55
>
> "I found the vendor branch concept a bit confusing;" -
> http://techlog.p2061.org/2008/05/21/using-svn-for-application-deployment/
>
>
>
> That's not to say it can't be improved in places. The writers welcome
> feedback. You should send it to the book mailing list. Info about how to do
> that is near the bottom of http://svnbook.org/ .
>
>
> If it was a wiki I'd contribute. Indeed, probably the people who wrote those
> blog posts would contribute.
>
> A wiki is not a substitute for a book either. A book is written and reviewed
>> by editors and formatted carefully and organized and changes are considered
>> before being accepted. Wikis accept all changes, some of which should never
>> have been accepted, or should have been in different places, or do not match
>> the style of the rest of the document. Especially in the case of the
>> Subversion book, I wouldn't change its process. I find it excellent.
>>
>
> The three bloggers plus myself would likely have contribute to the wiki page
> on Subversion Branches. How many people write the Subversion Book? A wiki
> would not substitute the book, it would complement it, by providing raw
> material, tools and useful distinctions.
>
> Just wanted to share my thoughts. I'm off to use Piston now. (Thanks Blair)
>
> Martin
> --
> Martin Cleaver M.Sc. MBA
>
> PS. Here's the script I wrote.
>
> cat svn_create_vendor_branch.pl
> #! /bin/perl -w
> use strict; # don't use this, use Piston http://piston.rubyforge.org/
>
> my $vendorurl="http://svn.automattic.com/wordpress-mu";
> my $vendordroptag="1.2.3";
>
> my $workingarea="/tmp/build-$$";
> mkdir $workingarea;
> chdir $workingarea;
>
> my $repodir=$workingarea.'/repo';
>
> my $repobase="file://$repodir";
> my $reponame="mysite.com";
> my $repourl="$repobase/$reponame";
>
> my $repovendor=$repourl.'/vendor';
> my $repowpmu=$repovendor.'/wpmu';
> my $repomucurrent=$repowpmu.'/current';
>
> my $repoproject=$repourl.'/project';
>
> if ( ! -d $repodir ) {
> mkdir $repodir
> }
>
> chdir $repodir;
> run ("svnadmin create $reponame");
>
> run ("svn mkdir $repovendor -m 'All code from others than me'");
> run ("svn mkdir $repowpmu -m 'Code from the $vendorurl wpmu team at
> Automattic'");
> run ("svn mkdir $repomucurrent -m 'Dir for wpmu current revision'");
>
>
> export_and_load($vendorurl, $vendordroptag);
>
> run ("svn cp $repomucurrent $repoproject -m 'Import of vendor branch
> $vendorurl $vendordroptag'");
>
> my $testcheckout=$workingarea."/checkout";
> mkdir $testcheckout;
> chdir $testcheckout;
>
> run ("svn co $repourl");
>
> print "Checked out to $testcheckout\n";
>
> part2();
>
> run ("find . -type d | grep -v .svn");
>
> sub part2 {
> my @vendordroptags=qw(1.2.4 1.2.4rc1 1.2.5 1.2.5a 1.3 1.3.2
> 1.3.3 1.5-rc1 1.5.1);
> foreach $vendordroptag (@vendordroptags) {
> export_and_load($vendorurl, $vendordroptag);
> }
> }
>
> sub export_and_load {
> my ($vendorurl, $vendordroptag) = @_;
> chdir $workingarea;
> run ("svn export $vendorurl/tags/$vendordroptag/");
> run ("svn_load_dirs.pl $repowpmu -t wpmu-$vendordroptag current
> ./$vendordroptag");
> }
>
> sub run {
> my ($cmd) = @_;
> print $cmd."\n";
> system $cmd;
> }
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
[PATCH] index.html (was: Re: A wiki for this group)
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
[[ Moving the thread to dev@; original thread is at [1]. ]]
Martin@Cleaver.org wrote on Thu, 7 Aug 2008 at 10:16 -0400:
> Ok.
> How about this?
>
> svn diff index.html
> Index: index.html
> ===================================================================
> --- index.html (revision 32394)
> +++ index.html (working copy)
> @@ -133,6 +133,8 @@
> >FAQ</a> (answers to Frequently Asked Questions)</li>
> <li><a href="http://svnbook.red-bean.com/"
> >Subversion Book</a> (complete online)</li>
> + <li><a href="http://www.orcaware.com/svn/wiki/Main_Page"
> + >Subversion Wiki (occasionally contributions are collated into the
> book)</li>
> <li>Chat room: <a href="irc://irc.freenode.net/svn"
> ><tt>irc.freenode.net</tt> (channel <tt>#svn</tt>)</a></li>
> <li>Subversion <a href="issue-tracker.html#find"
>
Martin said upthread that he added the wiki's URL to the /topic of #svn
this morning.
Daniel
[1] http://search.gmane.org/?query=A%20wiki%20for%20this%20group&group=gmane.comp.version-control.subversion.user&sort=date
> Regards,
> Martin.
> --
> Martin@Cleaver.org
> +1 416-786-6752 (GMT-5)
>
>
>
> On Thu, Aug 7, 2008 at 2:22 AM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
>
> > Ryan Schmidt wrote on Wed, 6 Aug 2008 at 17:19 -0500:
> > > On Aug 6, 2008, at 14:43, Martin@Cleaver.org wrote:
> > >
> > > > The existing site is somewhat broken. For instance from
> > > > http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=121964
> > > > I click "Contributed tools" and get taken to the 404 at
> > > > http://subversion.tigris.org/servlets/tools_contrib.html ; if
> > > > the site was a wiki more people could help to maintain the site
> > > > structure.
> > >
> > > I can confirm that this is broken. Attached is a patch to fix
> > > this. Perhaps someone with commit access to the repository would
> > > commit it.
> > >
> >
> > Committed as r32393. Thanks!
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: A wiki for this group
Posted by "Martin@Cleaver.org" <Ma...@Cleaver.org>.
Ok.
How about this?
svn diff index.html
Index: index.html
===================================================================
--- index.html (revision 32394)
+++ index.html (working copy)
@@ -133,6 +133,8 @@
>FAQ</a> (answers to Frequently Asked Questions)</li>
<li><a href="http://svnbook.red-bean.com/"
>Subversion Book</a> (complete online)</li>
+ <li><a href="http://www.orcaware.com/svn/wiki/Main_Page"
+ >Subversion Wiki (occasionally contributions are collated into the
book)</li>
<li>Chat room: <a href="irc://irc.freenode.net/svn"
><tt>irc.freenode.net</tt> (channel <tt>#svn</tt>)</a></li>
<li>Subversion <a href="issue-tracker.html#find"
Regards,
Martin.
--
Martin@Cleaver.org
+1 416-786-6752 (GMT-5)
On Thu, Aug 7, 2008 at 2:22 AM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
> Ryan Schmidt wrote on Wed, 6 Aug 2008 at 17:19 -0500:
> > On Aug 6, 2008, at 14:43, Martin@Cleaver.org wrote:
> >
> > > The existing site is somewhat broken. For instance from
> > >
> http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=121964 I
> > > click "Contributed tools" and get taken to the 404 at
> > > http://subversion.tigris.org/servlets/tools_contrib.html ; if the site
> was a
> > > wiki more people could help to maintain the site structure.
> >
> > I can confirm that this is broken. Attached is a patch to fix this.
> Perhaps
> > someone with commit access to the repository would commit it.
> >
>
> Committed as r32393. Thanks!
>
>
Re: A wiki for this group
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Ryan Schmidt wrote on Wed, 6 Aug 2008 at 17:19 -0500:
> On Aug 6, 2008, at 14:43, Martin@Cleaver.org wrote:
>
> > The existing site is somewhat broken. For instance from
> > http://subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=121964 I
> > click "Contributed tools" and get taken to the 404 at
> > http://subversion.tigris.org/servlets/tools_contrib.html ; if the site was a
> > wiki more people could help to maintain the site structure.
>
> I can confirm that this is broken. Attached is a patch to fix this. Perhaps
> someone with commit access to the repository would commit it.
>
Committed as r32393. Thanks!
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: A wiki for this group
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Aug 6, 2008, at 14:43, Martin@Cleaver.org wrote:
> The existing site is somewhat broken. For instance from http://
> subversion.tigris.org/servlets/ReadMsg?listName=dev&msgNo=121964 I
> click "Contributed tools" and get taken to the 404 at http://
> subversion.tigris.org/servlets/tools_contrib.html ; if the site was
> a wiki more people could help to maintain the site structure.
I can confirm that this is broken. Attached is a patch to fix this.
Perhaps someone with commit access to the repository would commit it.
FYI the Tigris site is not the best way to read the mailing list
archive. http://svn.haxx.se/ is better.