From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] usage of git to send patches to u-boot mailinglist
Date: Thu, 10 Jul 2008 11:00:48 +0200 [thread overview]
Message-ID: <20080710090048.CF75F248FE@gemini.denx.de> (raw)
In-Reply-To: Your message of "Thu, 10 Jul 2008 08:21:49 +0800." <20080710002148.GD4657@prithivi.gnumonks.org>
In message <20080710002148.GD4657@prithivi.gnumonks.org> you wrote:
>
> can do, even though I believe it is by far not the best tool to do so.
The definition of "the best tool" depends on many things, including
previous experience and personal preferences.
> The problem is that I would have to use one local branch per feature
> (i.e. lots of local branches that need to be kept in sync), and even
> then any incremental changes/fixes to one particular feature are visible
> in the commitlog (and thus result in changelog pollution).
Having many local branches is no problem with git.
Git provides excellent help to rebase such branches, and using
"--interactive" gives you a lot of options to edit the history.
> So is this really the preferred workflow? How are others dealing with
> this? How to avoid commitlog pollution?
I started using "git-rebase -i", and so far it seems to work fine for
me. But I'm definitely not an expert.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Contrary to popular belief, thinking does not cause brain damage.
prev parent reply other threads:[~2008-07-10 9:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-06 17:06 [U-Boot-Users] [PATCH] Remove code duplication for setting the default environment Harald Welte
2008-07-06 18:57 ` Wolfgang Denk
2008-07-07 7:40 ` Harald Welte
2008-07-09 22:30 ` Wolfgang Denk
2008-07-10 0:21 ` [U-Boot-Users] usage of git to send patches to u-boot mailinglist Harald Welte
2008-07-10 4:36 ` Paul Gortmaker
2008-07-10 8:34 ` Markus Klotzbücher
2008-07-10 8:49 ` Stefan Roese
2008-07-10 9:00 ` Wolfgang Denk [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=20080710090048.CF75F248FE@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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