From: Jan Kiszka <jan.kiszka@siemens.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Laurent Desnogues <laurent.desnogues@gmail.com>,
Christoph Egger <Christoph.Egger@amd.com>,
"C.W. Betts" <computers57@hotmail.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: updating git tree
Date: Tue, 28 Apr 2009 12:20:48 +0200 [thread overview]
Message-ID: <49F6D880.1060409@siemens.com> (raw)
In-Reply-To: <49F6D493.9050806@redhat.com>
Kevin Wolf wrote:
> Jan Kiszka schrieb:
>> Christoph Egger wrote:
>>> On Tuesday 28 April 2009 08:54:56 Laurent Desnogues wrote:
>>>> On Tue, Apr 28, 2009 at 8:50 AM, C.W. Betts <computers57@hotmail.com> wrote:
>>>>> I'm feeling lazy and I don't want to look at all the e-mails. How do you
>>>>> update your git tree?
>>>> Once you've cloned it (aka checkout), you update your tree using git pull
>>>> (aka update).
>>> Unlike 'svn update', a 'git pull' doesn't automatically merge local changes.
>>> git fails instead. git is missing this 'automatic merge on pull' feature.
>>> If you have local changes, you must do
>>>
>>> git stash ; git pull ; git stash pop
>>>
>>> Christoph
>>>
>>> P.S.: With mercurial you do 'hg pull -u' and local changes are automatically
>>> merged.
>> If you have non-trivial changes pending, probably in multiple commits, I
>> can only recommend using stgit (or guilt) to compensate the missing
>> patch queue feature of git. It allows you to easily navigate back and
>> forth in your patch queues before finally posting them.
>
> I haven't used these yet. Is there a real benefit compared to using a
> normal git branch and rebase -i? Maybe I should try them if so.
I'm not only talking about rebasing, also about working within your
patch queue, editing patches in their middle, splitting it up,
reordering it etc. There are surely ways to do this with native git
(stgit is just a front-end and uses normal git), but that's not done
with two or three git commands.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-04-28 10:21 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <77A0C157-5334-4505-BDDA-324862C1E429@hotmail.com>
2009-04-28 6:50 ` [Qemu-devel] updating git tree C.W. Betts
2009-04-28 6:54 ` Laurent Desnogues
2009-04-28 7:21 ` Bartlomiej Celary
2009-04-28 8:49 ` Christoph Egger
2009-04-28 9:32 ` Kevin Wolf
2009-04-28 9:38 ` [Qemu-devel] " Jan Kiszka
2009-04-28 9:42 ` Laurent Desnogues
2009-04-28 10:04 ` Kevin Wolf
2009-04-28 10:20 ` Jan Kiszka [this message]
2009-04-28 10:28 ` Kevin Wolf
2009-04-28 10:48 ` Jan Kiszka
2009-04-28 10:58 ` Kevin Wolf
2009-04-28 11:14 ` Jan Kiszka
2009-04-28 11:15 ` François Revol
2009-04-28 10:25 ` Gerd Hoffmann
2009-04-28 11:11 ` [Qemu-devel] " François Revol
2009-04-28 12:03 ` Laurent Desnogues
2009-04-28 12:57 ` François Revol
2009-04-28 13:10 ` Laurent Vivier
2009-04-28 13:49 ` François Revol
2009-04-28 13:58 ` Kevin Wolf
2009-04-28 15:10 ` Laurent Vivier
2009-04-28 15:22 ` Kevin Wolf
2009-04-28 15:40 ` Laurent Vivier
2009-04-28 16:51 ` Andreas Färber
2009-04-28 19:25 ` François Revol
2009-04-28 19:49 ` Andreas Färber
2009-04-28 20:17 ` François Revol
2009-04-28 21:01 ` François Revol
2009-04-29 7:54 ` Markus Armbruster
2009-04-29 8:51 ` François Revol
2009-04-29 9:22 ` Markus Armbruster
2009-04-29 9:57 ` François Revol
2009-04-29 7:44 ` Markus Armbruster
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=49F6D880.1060409@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Christoph.Egger@amd.com \
--cc=computers57@hotmail.com \
--cc=kwolf@redhat.com \
--cc=laurent.desnogues@gmail.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).