[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-librejs] Making changes to the Savannah repo
From: |
Thomas Harding |
Subject: |
Re: [Bug-librejs] Making changes to the Savannah repo |
Date: |
Fri, 04 Aug 2017 00:45:20 +0200 |
User-agent: |
K-9 Mail for Android |
Le 3 août 2017 23:30:33 GMT+02:00, Nathan Nichols <address@hidden> a écrit :
> >
> > Savannah has a BTS, filling a bug report (on project, not Savannah)
> and
> > attach
> > a patch is the standard way.
> > nongnu simply follows GNU projects way : having maintainers. Note
> you can
> > enlist several keys on project.
> > Note also Project Savannah has itself a mailing list and probably
> relies
> > on BTS
> > where you can fill feature requests. Main keys to Savannah
> management are
> > disk
> > room and bandwidth (almost no fees).
>
>
> So you are saying I should submit changes to here and just attach the
> changed source files?
>
> https://savannah.gnu.org/bugs/?func=additem&group=librejs
Yep : provided the librejs project maintainer (which by default will receive a
mail notification) will push the patch on git/svn/cvs, whatether repository is
used.
That's the only way to ensure code review.
That's alsi why project maintainers exists ^^
>
> On Wed, Aug 2, 2017 at 5:48 PM, Nathan Nichols
> <address@hidden>
> wrote:
>
> > Most of what is up right now in the web-ext branch is already
> outdated. I
> > would like to submit today's progress.
> >
> > How do I go about doing this?
> >
--
Je suis née pour partager, non la haine, mais l'amour
-- Sophocle (Antigone)