public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Good first bugs - beginner questions
Date: Fri, 30 Oct 2015 16:08:23 +0000	[thread overview]
Message-ID: <1446221303.2626.185.camel@ipfire.org> (raw)
In-Reply-To: <DUB117-W4858CC83A667E12619EE319C2F0@phx.gbl>

[-- Attachment #1: Type: text/plain, Size: 1805 bytes --]

Hi,

On Fri, 2015-10-30 at 08:10 +0100, Blago Culjak wrote:
> Hello, I have tried to squash some GoodFirstBugs, and did it
> sucessfully on couple of them, but process of submiting patches was
> very hard and couldn't make it all the way to the end.

That is okay. These might be sometimes a bit difficult, but it wouldn't
be that much fun without the challenge :)

> 
> Since this is my first time that I'm doing git, and I'm Windows user,
> following all the steps described on wiki was not enough (unleast for
> me, I know you are experts) to submit anything. Collague Larsen did
> tried to explaing me in short, but still, sending in patches was not
> working.
> 
> So my first question, can someone make a video tutorial on Windows
> about setting up git and submiting patches? How about on Linux?

I am not using Windows.

> Other issue, is that sometime I have short questions, they may seems 
> stupid to some of you, but I think you said that we can have an 
> mentor in begining, or someone we can ask questions.

Please do ask these questions. Everyone went through this phase and
especially git can be sometimes a bit difficult at the beginning. Just
try to solve one thing at a time and make small steps. Larsen is also
right on that a good description about what is not working. You will
need to help us to help you. This will also be indexed by the search
engines and hopefully help other people who have the same issue because
they can find this conversation.

> One type of question I'm waiting for answer is here:
> https://bugzilla.ipfire.org/show_bug.cgi?id=10900

I replied to that one just now.

> It would be good if I could ping someone quickly, by some IM to know
> I'm going in right direction.
> 
> Hope my question didn't frustrate you too much.

It didn't.

> 
> BR

-Michael

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

      parent reply	other threads:[~2015-10-30 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DUB117-W4858CC83A667E12619EE319C2F0@phx.gbl>
2015-10-30  9:45 ` Larsen
2015-10-30 16:08 ` Michael Tremer [this message]

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=1446221303.2626.185.camel@ipfire.org \
    --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