From: "Andreas Bießmann" <andreas.devel@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] AT91SAM9XE add embedded flash support
Date: Mon, 09 Aug 2010 09:46:18 +0200 [thread overview]
Message-ID: <4C5FB24A.9020702@googlemail.com> (raw)
In-Reply-To: <4C5FB0B2.6030000@emk-elektronik.de>
Dear Reinhard Meyer,
Am 09.08.2010 09:39, schrieb Reinhard Meyer:
> Dear Andreas Bie?mann
>> Ah, i see ... you have uncommited changes in your current branch? Bad
>> thing!
>
> Umm, the current branch would always have WIP. Always committing half done
> work to fix a problem in another branch seems tedious to me. Doing that I
> would have many dozen commits by now that I would have to squash later.
> Is that really the only way to go?
Well you need to have a clean "Working Copy" (as it is called in SVN) to
do the git tricks rebase a.s.o. Therefore you need to commit changes
before doing the rework. Therefore it would be best to have a single
branch collecting the patches to go upstream. This branch can be used to
rework a patch for next submission.
But there is another solution. You can have a seperate repository ...
When you use 'git clone' switches --local, --shared and --reference you
can safe disk space.
>
> Reinhard
Andreas
next prev parent reply other threads:[~2010-08-09 7:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 7:47 [U-Boot] [PATCH v2] AT91SAM9XE add embedded flash support Reinhard Meyer
2010-08-08 21:51 ` Wolfgang Denk
2010-08-09 5:13 ` Reinhard Meyer
2010-08-09 6:34 ` Andreas Bießmann
2010-08-09 7:08 ` Reinhard Meyer
2010-08-09 7:28 ` Andreas Bießmann
2010-08-09 7:39 ` Reinhard Meyer
2010-08-09 7:43 ` Alessandro Rubini
2010-08-09 7:46 ` Andreas Bießmann [this message]
2010-08-09 7:28 ` Andreas Bießmann
2010-08-09 16:00 ` [U-Boot] [PATCH v3] AT91SAM9XE: " Reinhard Meyer
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=4C5FB24A.9020702@googlemail.com \
--to=andreas.devel@googlemail.com \
--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