From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] lftp: new package.
Date: Mon, 25 Nov 2013 18:54:04 +0100 [thread overview]
Message-ID: <52938EBC.5050407@mind.be> (raw)
In-Reply-To: <1385384136-22652-1-git-send-email-rebillout@syscom.ch>
Hi Arnaud,
On 25/11/13 13:55, Arnaud R?billout wrote:
> Here comes a second version of the patch to include lftp in buildroot.
>
> Improvements from v1:
> * Config.in
> * Typo corrected
> * lftp.mk
> * LFTP_SOURCE removed
> * LFTP_AUTORECONF set to YES
> * POST_INSTALL_TARGET factorized a lot
> * patches:
> * Signed-off
> * Patch the m4 file instead of the configure script
Such a changelog is normally included in the patch commit message
itself, like so:
lftp: new package
LFTP is a sophisticated ftp/http client, and a file transfer program
...
Signed-off-by: ...
---
v2:
* Config.in: typo corrected
* ...
The part below --- is not included in the git history when Peter
commits it.
The advantage of this approach is that you can keep the history around
when you send v3 etc. of the patch. You update the patch using 'git
commit --amend' or 'git rebase -i', and in the commit message you add the
history below the --- line. On your side, the part below --- *will* be
kept in the git history, so the next time you use git send-email,
everything will be there.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
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
prev parent reply other threads:[~2013-11-25 17:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 12:55 [Buildroot] [PATCH v2] lftp: new package Arnaud Rébillout
2013-11-25 12:55 ` [Buildroot] [PATCH] " Arnaud Rébillout
2013-11-25 17:59 ` Arnout Vandecappelle
2013-12-02 9:36 ` Arnaud Rébillout
2013-12-02 22:04 ` Arnout Vandecappelle
2013-12-03 7:59 ` Arnaud Rébillout
2013-11-25 17:54 ` Arnout Vandecappelle [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=52938EBC.5050407@mind.be \
--to=arnout@mind.be \
--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