From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: GitHub Pull Requests?
Date: Sat, 14 Jun 2014 19:55:59 +0200 [thread overview]
Message-ID: <1402768559.6967.21.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <CAMtaDYQpbCS9PeRoJLxVY-RUWbpHvvZYv89Yh-qOo5NZok3HYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
Hi Stefan,
thanks for your submission.
Indeed GitHub Pull requests are not the best way for us to handle those.
GitHub is still not able to send us notifications when a new pull
request is created. We don't use it for anything else than just
mirroring our repositories to there.
That means you can use pull requests, but always open a bug report in
our own bugtracker and reference both to each other. In that way, we can
track GitHub pull requests just as we do it with everything else like
assinging them to people who will take care of those and you can use
your own repositories on GitHub.
If you could please do that we can start looking into the matter.
Best,
-Michael
On Sat, 2014-06-14 at 19:01 +0200, Stefan Ferstl wrote:
> Hi
>
> I recently had some troubles with my OpenVPN certificates on IPFire. I
> could easily fix the problem with a one-liner in OpenVPN's "verify"
> script.
> Additionally, I filed a pull request [1] on GitHub with that solution.
> Since there hasn't been any reaction at all whatsoever for more than
> one month now, I want to ask if I have to submit a patch over a
> different channel than via GitHub.
>
>
> Cheers,
> Stefan
>
>
> [1] https://github.com/ipfire/ipfire-2.x/pull/25
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development
next prev parent reply other threads:[~2014-06-14 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 17:01 Stefan Ferstl
2014-06-14 17:55 ` Michael Tremer [this message]
2014-06-15 13:53 Stefan Ferstl
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=1402768559.6967.21.camel@rice-oxley.tremer.info \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox