All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Dan Williams <dcbw@redhat.com>,
	linux-wireless@vger.kernel.org,
	Holger Schurig <hs4233@mail.mn-solutions.de>,
	libertas-dev@lists.infradead.org
Subject: Re: [PATCH] less eventcause shifts
Date: Tue, 4 Dec 2007 11:12:31 -0500	[thread overview]
Message-ID: <20071204161231.GI19911@tuxdriver.com> (raw)
In-Reply-To: <1196782170.13978.296.camel@pmac.infradead.org>

On Tue, Dec 04, 2007 at 03:29:30PM +0000, David Woodhouse wrote:

> Basically, trees which get rebased aren't suitable for git users to base
> their work on. It just doesn't work.

Well I think that is an overstatement, but you are entitled to it... :-)

I don't know what else I can offer.  There may be some ways to
rebase 'everything' less often, but I don't think I can eliminate it
completely without having a big mess.

> Which is why I thought we'd agreed that I'll commit libertas-related
> stuff to libertas-2.6.git for now, where Holger and I can play to our
> hearts' content, then ask you to pull when we're done.

I just don't see where I have upset that apple cart.  Polish-up your
tree and I'll pull it.  I (or maybe we) will work it out from there.

Again, I don't have any more libertas patches in queue.  So don't
send any more until you are ready to merge and I don't think there
will be a serious problem.

> I'm open to better suggestions, as long as they're not "you are not
> allowed to use git, except as a primitive way of storing patches". :)

Keeping a clean patch stack at the top is the only way I know to
come close to guaranteeing you have mergeable patches.  Beyond that,
I'll work with you the best that I can.

John
-- 
John W. Linville
linville@tuxdriver.com

  parent reply	other threads:[~2007-12-04 16:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28  8:15 [PATCH] less eventcause shifts Holger Schurig
2007-11-28 14:53 ` Dan Williams
2007-11-28 15:02   ` David Woodhouse
2007-11-28 15:13     ` Holger Schurig
2007-11-28 15:22       ` Dan Williams
2007-11-28 16:29       ` David Woodhouse
2007-11-29  9:32         ` Holger Schurig
2007-11-28 15:21     ` Dan Williams
2007-12-03 17:58 ` Dan Williams
2007-12-03 20:48   ` David Woodhouse
2007-12-03 21:17     ` Dan Williams
2007-12-04 14:54     ` John W. Linville
2007-12-04 15:07       ` David Woodhouse
2007-12-04 15:06         ` Dan Williams
2007-12-04 15:21           ` David Woodhouse
2007-12-04 15:11         ` David Woodhouse
2007-12-04 15:21         ` John W. Linville
2007-12-04 15:29           ` David Woodhouse
2007-12-04 16:00             ` Dan Williams
2007-12-04 16:14               ` John W. Linville
2007-12-04 16:17                 ` Dan Williams
2007-12-04 16:12             ` John W. Linville [this message]
2007-12-04 16:27               ` [PATCH] fewer " David Woodhouse
2007-12-04 16:57                 ` John W. Linville

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=20071204161231.GI19911@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=dcbw@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.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.