[Debtags-devel] Re: offering help with debtags

Enrico Zini enrico@debian.org
Wed, 8 Jun 2005 23:57:03 +0200

Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

[Hello everyone!  Let me introduce you to Phill Atwood, who offered to
 help and will try to take care of the web pages of debtags.
 Phill, welcome in the list!]

On Sat, Jun 04, 2005 at 06:38:27PM -0400, Phill Atwood wrote:
> >The webpages are currently maintained in subversion at
> >svn://svn.debian.org/debtags/web, and there's a hook that updates the
> >web pages when they are committed.  Once you register an account at
> >alioth.debian.org, I can give you commit access and you can play around.
> I've registered an account now at alioth.  The account name is=20
> phillatw-guest.

Great!  I added you to the project and gave you commit access.  Please
tell me about any problems you might have.

The write address of the web in subversion is:


You may need to explicitly use the username:


> I was curious to see that your paper was done in reStructuredText=20
> format.  I don't know much about it but I did attend a python talk a=20
> year ago where they covered it.  It seemed quite useful.

Yes, it's nice in that you can just turn an e-mail or a couple of notes
into an article without changing the editor :)  And I can also put the
same contents on, say, the README or FAQ file in the package as well as
on a webpage.

> >If you don't like subversion or prefer to maintain the website in some
> >other way, I'm happy to do it your way.
> Unfortunately, it's been 15 years since I've used a source code control=
> system in Unix.  If cvs goes back that far maybe it was cvs. More=20
> recently,  unfortunately, it was SourceSafe a few years ago. Anyways,=20
> I'm happy to try to figure out subversion.

Luckily enough, it's quite easy: just replace cvs with svn and 90% of
commands are the same.  The remaining 10% are things one always wanted
=66rom cvs, like "svn mv" :)

Plus, there's no special handling for HEAD or branches and tags, but
it's just a file space with revision tracking: "trunk" is the
conventional name of the directory where HEAD development happens, while
"tags" is the conventional name of the directory where tags are made
(just by copying a specific version of the thrunk in there) and similar
happens with "branches".

Anyway, feel free to try things around and ask for help.

> >Do you want to move this discussion to the mailing list?
> I think we should.

Great!  I replied to the list.



GPG key: 1024D/797EBFAB 2000-12-05 Enrico Zini <enrico@enricozini.org>

Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

Version: GnuPG v1.4.1 (GNU/Linux)