From: Felipe Balbi <me@felipebalbi.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Greg KH <greg@kroah.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
USB list <linux-usb@vger.kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: The gregkh patch scripts
Date: Mon, 8 Mar 2010 08:04:06 +0200 [thread overview]
Message-ID: <20100308060405.GA3885@gandalf> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1003071546000.8502-100000@netrider.rowland.org>
Hi,
On Sun, Mar 07, 2010 at 03:54:25PM -0500, Alan Stern wrote:
> Let's ask some other people on the USB list (CC'ed). My main concern
> is to avoid rebasing too often, whichever source-code management system
> is used.
personally, I'm more used to git and find it difficult (or annoying) when
I need to rebase my own patches on top of Greg's quilt tree. git
quiltimport doesn't work always and I have to refresh patches on my own
and run git quiltimport later again.
Moving to a git tree would help me, but then again, I don't want to
become a burden. Whatever is better for Greg, I'll be adapating to ;-)
What I use currently to have a tree which people can pull from and still
be able to rebase on top of Greg's patches is something like:
$ git fetch linus
$ git reset --hard linus/master
$ git quiltimport --patches gregkh
$ git rebase greg my_patches
$ git merge -s ours master
$ git checkout master
$ git merge my_patches
it helps although rebuilding the tree always is a bit messy :-p
--
balbi
next prev parent reply other threads:[~2010-03-08 6:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 4:19 The gregkh patch scripts Alan Stern
2010-03-07 18:16 ` Greg KH
2010-03-07 20:54 ` Alan Stern
2010-03-08 6:04 ` Felipe Balbi [this message]
2010-03-09 19:50 ` Greg KH
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=20100308060405.GA3885@gandalf \
--to=me@felipebalbi.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.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 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.