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: [PATCH] arping: Update to 2.15
Date: Sat, 12 Dec 2015 12:59:40 +0000	[thread overview]
Message-ID: <1449925180.31655.136.camel@ipfire.org> (raw)
In-Reply-To: <566C1886.1060406@ipfire.org>

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

Yes, you can manually edit them and add what ever is needed.

I hope that my talk from the last developer summit will soon be
available where I explain why these are all there. You can find the
slides here, but these are probably not enough:

  http://people.ipfire.org/~ms/talks/2015_-_Submitting_Patches.pdf

Otherwise this can be found here in a longer text:

  http://wiki.ipfire.org/devel/git/tags

Best,
-Michael

On Sat, 2015-12-12 at 13:52 +0100, Matthias Fischer wrote:
> Hi Michael,
> 
> On 12.12.2015 13:40, Michael Tremer wrote:
> > You could express this by adding an other Signed-off-by line with
> > Erik's details...
> > 
> > Do you want to resend the patch?
> 
> Yes. I never did this before, but I can try... ;-)
> 
> As I understand:
> 
> I add another line, saying:
> 
> ...
> Signed-off-by: Erik Kapfer <ummeegge(a)ipfire.org>
> ...
> 
> Would that be sufficient?
> 
> Best,
> Matthias
> 

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

       reply	other threads:[~2015-12-12 12:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <566C1886.1060406@ipfire.org>
2015-12-12 12:59 ` Michael Tremer [this message]
2015-12-12 13:10 Matthias Fischer
2015-12-12 13:12 ` Michael Tremer
2015-12-12 13:42   ` Matthias Fischer
  -- strict thread matches above, loose matches on Subject: below --
2015-12-12 12:32 Matthias Fischer
2015-12-12 12:40 ` 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=1449925180.31655.136.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