From: Haavard Skinnemoen <hskinnemoen@atmel.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Tilman Schmidt <tilman@imap.cc>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: git guidance
Date: Thu, 29 Nov 2007 00:22:45 +0100 [thread overview]
Message-ID: <20071129002245.33096661@siona> (raw)
In-Reply-To: <Pine.LNX.4.64.0711280019200.4181@fbirervta.pbzchgretzou.qr>
On Wed, 28 Nov 2007 00:20:46 +0100 (CET)
Jan Engelhardt <jengelh@computergmbh.de> wrote:
> On Nov 27 2007 23:33, Tilman Schmidt wrote:
> >
> >It didn't work too well. The first result was one of maximal
> >embarrassment: I produced a patch that didn't even compile when
> >applied to the official tree. This shouldn't happen with git, right?
> >Well, it did. So now I'm back to keeping a virgin kernel source tree
> >alongside my development area in order to produce diffs. That can't
> >be right?
> >
> No, it can't. Use stgit/quilt ;p
No, use "git rebase --interactive" ;-)
I've tried stgit/guilt/quilt as well, but I could never quite get the
hang of it (adding the files _before_ editing is the difficult part.) On
the other hand, git rebase --interactive fit right into my workflow and
improved it massively.
But I guess it's all a matter of personal preference.
Haavard
next prev parent reply other threads:[~2007-11-28 23:23 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-27 22:33 git guidance Tilman Schmidt
2007-11-27 22:54 ` J. Bruce Fields
2007-11-27 22:55 ` Kristoffer Ericson
2007-11-27 23:52 ` Willy Tarreau
2007-11-28 0:43 ` Kristoffer Ericson
2007-11-28 0:49 ` Randy Dunlap
2007-11-28 12:49 ` Al Boldi
2007-11-28 13:45 ` Rogan Dawes
2007-11-28 15:46 ` Johannes Schindelin
2007-11-28 17:14 ` Al Boldi
2007-11-28 18:14 ` Johannes Schindelin
2007-11-28 18:30 ` Al Boldi
2007-11-28 18:41 ` Jakub Narebski
2007-11-28 18:41 ` Jakub Narebski
2007-11-29 5:27 ` Al Boldi
2007-11-29 12:57 ` Kyle Moffett
2007-11-28 13:38 ` Tilman Schmidt
2007-11-28 21:20 ` Willy Tarreau
2007-11-28 11:23 ` Tilman Schmidt
2007-11-28 12:31 ` Kristoffer Ericson
2007-11-27 23:20 ` Jan Engelhardt
2007-11-28 15:15 ` Dave Quigley
2007-11-28 15:57 ` Tilman Schmidt
2007-11-28 16:37 ` Dave Quigley
2007-11-28 19:10 ` willem
2007-11-28 19:18 ` Dave Quigley
2007-11-28 23:22 ` Haavard Skinnemoen [this message]
2007-11-29 12:45 ` Tilman Schmidt
2007-11-29 13:03 ` Haavard Skinnemoen
2007-11-28 7:41 ` Arkadiusz Miskiewicz
2007-11-29 12:51 ` Tilman Schmidt
-- strict thread matches above, loose matches on Subject: below --
2007-11-29 15:52 Jing Xue
2007-11-29 16:19 ` Linus Torvalds
2007-12-01 6:50 ` Al Boldi
2007-12-04 22:21 ` Phillip Susi
2007-12-07 17:35 ` Al Boldi
2007-12-06 18:24 ` Andreas Ericsson
2007-12-07 18:55 ` Al Boldi
2007-12-06 20:22 ` Johannes Schindelin
2007-12-07 4:37 ` Al Boldi
2007-12-07 8:40 ` Andreas Ericsson
2007-12-07 10:53 ` Al Boldi
2007-12-07 11:47 ` Jakub Narebski
2007-12-07 19:04 ` Al Boldi
2007-12-07 19:36 ` Valdis.Kletnieks
2007-12-07 22:07 ` Luke Lu
2007-12-08 4:56 ` Al Boldi
2007-12-08 5:16 ` Valdis.Kletnieks
2007-12-08 10:41 ` Al Boldi
2007-12-08 11:13 ` Johannes Schindelin
2007-12-07 12:30 ` Andreas Ericsson
2007-12-07 21:17 ` david
2007-12-07 22:00 ` Björn Steinbrink
2007-12-06 21:46 ` Phillip Susi
2007-12-08 6:33 ` Martin Langhoff
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=20071129002245.33096661@siona \
--to=hskinnemoen@atmel.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tilman@imap.cc \
/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.