From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] nano: Update to 2.4.2
Date: Sun, 26 Jul 2015 20:47:24 +0100 [thread overview]
Message-ID: <1437940044.19074.11.camel@ipfire.org> (raw)
In-Reply-To: <55B52967.3070503@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
Hi,
On Sun, 2015-07-26 at 20:39 +0200, Matthias Fischer wrote:
> Hi Michael,
>
> On 26.07.2015 19:58, Michael Tremer wrote:
> > The content is fine.
>
> At least something... ;-)
>
> > I merged this one since I manually edited it. Have you tried using
> > "git
> > send-email"?
>
> Sorry for the mess - I tried, but obviously my email client had other
> thoughts than me...
No worries.
>
> Will try "git send-email" next time. Any hints for the correct/wanted
> syntax? I'm using the terminal console most of the time.
> I've found something about using "hooks" - e.g., the file
> "commit-msg.sample" in directory '.git/hooks'.
You do not need any of that. Just set up your email account like
described here
http://wiki.ipfire.org/devel/git/setup
commit as usual and after that run "git send-email -1" with maybe some
more parameters. You can send emails to yourself for testing.
Make sure that your build system is up to date and has got the latest
version of Git (should be 2.4.4 or so).
It should be easy then...
-Michael
>
> But I'm not sure, if this is the right way to do it or if I have to
> make
> specific changes in this file.
>
> Regards
> Matthias
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2015-07-26 19:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55B52967.3070503@t-online.de>
2015-07-26 19:47 ` Michael Tremer [this message]
2015-07-26 14:43 Matthias Fischer
2015-07-26 17:58 ` 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=1437940044.19074.11.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