From: "Alf Høgemark" <alf@i100.no>
To: development@lists.ipfire.org
Subject: Re: What is the process for suggesting bug fixes and improvements (bugtracker vs gitbug) ?
Date: Tue, 11 Feb 2014 18:34:32 +0100 [thread overview]
Message-ID: <52FA5F28.1080301@i100.no> (raw)
In-Reply-To: <1391954463.21794.170.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]
On 02/09/2014 03:01 PM, Michael Tremer wrote:
>> Should I make an issue in the bug tracker for each of my pull
>> requests ?
>> Should I rather attach a patch to a bug tracker issue than issuing
>> pull requests on github ?
> Basically yes.
>
> This might depend a little bit on what the changes include, but I think
> the bugtracker is the best option for most cases. You may still use your
> GitHub repository and point to the branch that should be pulled. A set
> of patches for each commit is also fine.
>
Could you give some information about what branches you use on
git.ipfire.org ?
http://git.ipfire.org/?p=ipfire-2.x.git;a=summary
I see the "next" branch, the "master" branch, "core75" branch and for
example the "fifteen" branch.
I haven't found information about that on the wiki.
I would appreciate a few word about these branches.
Will 2.15 be "core76" ?
If I have some bug fixes for the current 2.13 core 75, what git branch
should I work against ?
The "core75" branch?
If I have some improvements that I think could maybe be part of 2.15,
what git branch should I work against ?
Regards
Alf
next prev parent reply other threads:[~2014-02-11 17:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52F735D7.9030709@i100.no>
2014-02-09 14:01 ` Michael Tremer
2014-02-11 17:34 ` Alf Høgemark [this message]
2014-02-12 19:04 ` Michael Tremer
2014-02-12 19:49 ` Alf Høgemark
2014-02-12 20:09 ` Michael Tremer
[not found] <aa65d969e7d74d3aaafea9e8fbff05c2.squirrel@webmail.mailadmin.no>
2014-02-17 16:28 ` Michael Tremer
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=52FA5F28.1080301@i100.no \
--to=alf@i100.no \
--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