public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Matthias Fischer <matthias.fischer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Sending in patches
Date: Tue, 12 Jan 2016 19:08:55 +0100	[thread overview]
Message-ID: <56954137.2040205@ipfire.org> (raw)
In-Reply-To: <1452462866.5665.3.camel@ipfire.org>

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

Hi,

On 10.01.2016 22:54, Michael Tremer wrote:
> I find this process with "git send-email" very easy...

Just a few "cents" from me... ;-)

I don't know how you would call it:

I'm doing it the "old-fashioned way": strictly by command-line, directly 
from GIT on my Ubuntu 'Devel'-PC. No GUI, no mouse, just console and 
keyboard. Nothing but blinking cursors and GIT commands.
git pull ..., git status ..., nano or mc-editor, make ..., git push ..., 
git sendmail ...: thats nearly all I use and need.

And after struggling through some - sometimes rather weird - problems, 
I'm getting used to it and wouldn't want to do it any other way.
Its logical and fast. Not comfortable, but 'at the roots'.

And while creating a patch for a new 'nano 2.5.1'-version 
(http://patchwork.ipfire.org/patch/208/) I got the thought that perhaps 
it would help others if I would ~record the process of creating this - 
rather easy - patch with some "how I did it" explanations and/or 
screenshots so they could get a grip on the procedure? Thinking of 
"Building Addons", perhaps we could put something like that in Wiki? Not 
too complicated, just showing how to build an rather easy patch and push 
it/send it through GIT.

Sorry, I got Windows 7 running, but none of the mentioned tools here, so 
my prerequisits may differ.

It would take some time, but I think, this could be a way to make things 
easier.

Jm2C

Best,
Matthias


  parent reply	other threads:[~2016-01-12 18:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-10 21:54 Michael Tremer
2016-01-11 20:40 ` Larsen
2016-01-15  1:25   ` Michael Tremer
2016-01-15  8:07     ` IT Superhack
2016-01-15 19:24       ` R. W. Rodolico
2016-01-16 14:45         ` Michael Tremer
2016-01-16 16:07         ` Matthias Fischer
2016-01-16 14:48       ` Michael Tremer
2016-01-16 18:07     ` Larsen
2016-01-17 19:17       ` Michael Tremer
2016-01-28 17:36         ` Larsen
2016-01-29  2:13           ` Michael Tremer
2016-01-12 18:08 ` Matthias Fischer [this message]
2016-01-15  1:28   ` Michael Tremer
     [not found] <DUB406-EAS128B6703A1A0778E8A258779CC90@phx.gbl>
2016-01-12 23:51 ` Michael Tremer
2016-01-13  4:39   ` Xaver4all
2016-01-15  1:29     ` Michael Tremer
     [not found] <DUB406-EAS163F3237DC6DE1AF244CD409CCE0@phx.gbl>
2016-01-16 14:53 ` 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=56954137.2040205@ipfire.org \
    --to=matthias.fischer@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