[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Create custom release section and add link to trademark policy

From: <kmradke_at_rockwellcollins.com>
Date: Fri, 8 Aug 2008 16:59:39 -0500

Karl Fogel <kfogel_at_red-bean.com> wrote on 08/08/2008 04:45:27 PM:
> "Kevin Radke" <kmradke_at_gmail.com> writes:
> > [[[
> > Add some guidelines about creating a custom release and include link
> > to trademark policy.
> >
> > *www/hacking.html
> > ]]]
>
> Kevin, the patch is all messed up (see quoted text below, which is
> exactly as I received it except for the "> " quotes along the left).
>
> Try re-attaching after tweaking your mailer in whatever way is
> necessary?

Hmm.... I just did an attach file with the gmail web interface. Figured
it would be much better than Notes at work... I'll resend with
thunderbird when I get home...

Kevin R.

>
> Thanks,
> -Karl
>
> > Index: www/hacking.html
=======================================================
> > ============ --- www/hacking.html (revision 32408) +++
www/hacking.html
> > (working copy) @@ -65,6 +65,7 @@
> > Stabilizing and maintaining releases
> > Signing source distribution packages
> > Localization (l10n) +
> > Creating a custom release
> > @@ -2962,6 +2963,24 @@
>http://svn.collab.net/repos/svn/trunk/TRANSLATING for
> > more information about translating.
> >
> > +
> > +
> >
> > Creating a custom release
> >
> > +
> >
> > It is preferred to use the patch process and have your changes
accepted +and
> > applied to trunk to be released on the normal Subversion release
schedule.
> > +However, if you feel that you need to make changes that would not be
+widely
> > accepted by the Subversion developer community or need +to provide
earlier
> > custom releases, you should follow some guidelines.
> >
> > + +
> >
> > First, make sure you follow the +Subversion trademark policy. You will
need to
> > differentiate your release +from the standard Subversion releases to
reduce any
> > potential confusion +caused by your custom release.
> >
> > + +
> >
> > Second, consider creating a branch in the public subversion repository
+to
> > track your changes and to potentially allow your custom changes to be
+merged
> > into the normal Subversion functionality.
> >
> > +
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> > For additional commands, e-mail: dev-help_at_subversion.tigris.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: dev-help_at_subversion.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-09 00:00:04 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.