Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rico Bachmann <bachmann@tofwerk.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Add libapr-package
Date: Tue, 24 Apr 2012 11:32:52 +0200	[thread overview]
Message-ID: <000301cd21fd$3941aba0$abc502e0$@com> (raw)
In-Reply-To: <201204211458.06684.arnout@mind.be>

> -----Urspr?ngliche Nachricht-----
> Von: Arnout Vandecappelle [mailto:arnout at mind.be]
> Gesendet: Samstag, 21. April 2012 14:58
> An: buildroot at busybox.net
> Cc: Rico Bachmann
> Betreff: Re: [Buildroot] [PATCH] Add libapr-package
> 
> On Tuesday 17 April 2012 16:35:15 Rico Bachmann wrote:
> >
> > Add libapr-package
> > rename from libapr to apr
> > rename all values and arguments from libapr into apr change
> > package/Config.in from libapr to apr add the other small changes from
> > mailinglist
> 
>  Hoi Rico,
> 
>  Thanks for your persistence in correcting your patch until it was
> perfect!
> 
>  One last suggestion for next time you make a patch: you can add the
> log of the history of your patch directly in the commit message, below
> a line with three dashes, like this:
> 
> Signed-off-by: Rico Bachmann <bachmann@tofwerk.com>
> ---
> v3: Rename from libapr to apr
> v2: ...

I'll try that with my new patch for apr-util.
How can I add my history when I have to do a git rebase -I master?

Because I can't see my history in the patch after a fixup with git rebase.

Do I have to add them manually?

> 
> 
>  When the patch is applied to git, the part below the --- will be
> removed, so you can also add other random comments in there.
> 
>  And also, you can add the version number when sending the patch like
> this:
> 
> git send-email --subject-prefix='PATCH v2' ...

I'll try that if I need a v2 from my next patch.

> 
> 
>  Regards,
>  Arnout
> 
> 
> --
> Arnout Vandecappelle                               arnout at mind be
> Senior Embedded Software Architect                 +32-16-286540
> Essensium/Mind                                     http://www.mind.be
> G.Geenslaan 9, 3001 Leuven, Belgium                BE 872 984 063 RPR
> Leuven
> LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
> GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

Thanks for the hints!

Regards
Rico

Tofwerk AG, Rico Bachmann
+41 33 511 11 69
bachmann at tofwerk.com
http://www.tofwerk.com
Uttigenstrasse 22
CH - 3600 Thun

  reply	other threads:[~2012-04-24  9:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17 14:35 [Buildroot] [PATCH] Add libapr-package Rico Bachmann
2012-04-17 14:35 ` [Buildroot] [PATCH] Add apr-package Rico Bachmann
2012-04-17 14:54   ` Peter Korsgaard
2012-04-21 12:58 ` [Buildroot] [PATCH] Add libapr-package Arnout Vandecappelle
2012-04-24  9:32   ` Rico Bachmann [this message]
2012-04-27 19:21     ` Arnout Vandecappelle
  -- strict thread matches above, loose matches on Subject: below --
2012-04-17 13:16 Rico Bachmann
2012-04-17 13:20 ` Baruch Siach
2012-04-17 13:26   ` Rico Bachmann
2012-04-17 13:29     ` Baruch Siach
2012-04-17 13:22 ` Yegor Yefremov
2012-04-17 13:29   ` Rico Bachmann
2012-04-17 13:25 ` Maxime Ripard
2012-04-17 13:35   ` Rico Bachmann
     [not found] <Re:[PATCH] Add libapr-package>
2012-04-17 10:59 ` Rico Bachmann
2012-04-17 11:36   ` Maxime Ripard
2012-04-17 12:18     ` Rico Bachmann
2012-04-17 11:39   ` Thomas Petazzoni
2012-04-17 12:01     ` Peter Korsgaard
2012-04-17 12:22       ` Rico Bachmann
2012-04-17 12:18     ` Rico Bachmann
2012-04-17 10:05 Rico Bachmann
2012-04-17 10:20 ` Yegor Yefremov
2012-04-17 10:25 ` Yegor Yefremov
2012-04-17 10:31   ` Rico Bachmann

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='000301cd21fd$3941aba0$abc502e0$@com' \
    --to=bachmann@tofwerk.com \
    --cc=buildroot@busybox.net \
    /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