From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] gnuplot : new package
Date: Mon, 7 Jan 2013 17:10:10 +0100 [thread overview]
Message-ID: <20130107171010.36ca678d@skate> (raw)
In-Reply-To: <50EAF1AC.8090907@syscom-instruments.com>
Dear Viallard Anthony,
On Mon, 07 Jan 2013 17:02:52 +0100, Viallard Anthony wrote:
> Sorry, i knew my post is not very sexy. This is because my git
> repository is very dirty and i don't known how clean my work.
All you need to learn is how to use "interactive rebase".
See
http://elinux.org/Buildroot_how_to_contribute#In_case_of_mistakes_in_my_branch
for a very basic introduction.
For more details, see
http://git-scm.com/book/en/Git-Tools-Rewriting-History#Changing-Multiple-Commit-Messages.
Once you know how to use interactive rebase, you can prepare very nice
patch series.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-07 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 13:30 [Buildroot] [PATCH 1/5] gnuplot : new package Anthony Viallard
2013-01-07 13:30 ` [Buildroot] [PATCH 2/5] gnuplot : disable inadequate options for embedded platform Anthony Viallard
2013-01-07 13:30 ` [Buildroot] [PATCH 3/5] gnuplot : move under "Graphic applications" section Anthony Viallard
2013-01-07 13:30 ` [Buildroot] [PATCH 4/5] gnuplot : add --without-doc and --without-demo options Anthony Viallard
2013-01-07 13:30 ` [Buildroot] [PATCH 4/4] gnuplot : add LICENSE things and new configure options Anthony Viallard
2013-01-07 13:48 ` [Buildroot] [PATCH 1/5] gnuplot : new package Thomas Petazzoni
2013-01-07 16:02 ` Viallard Anthony
2013-01-07 16:10 ` Thomas Petazzoni [this message]
2013-01-08 8:57 ` Viallard Anthony
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=20130107171010.36ca678d@skate \
--to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.