All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Kalle Valo <kalle.valo@nokia.com>
Cc: Zhu Yi <yi.zhu@intel.com>, linux-wireless@vger.kernel.org
Subject: Re: wireless-testing rebased again?
Date: Tue, 9 Sep 2008 10:05:56 -0400	[thread overview]
Message-ID: <20080909140556.GA4291@tuxdriver.com> (raw)
In-Reply-To: <873ak9hnux.fsf@nokia.com>

On Tue, Sep 09, 2008 at 08:47:34AM +0300, Kalle Valo wrote:
> John W. Linville <linville@tuxdriver.com> writes:
> 
> > On Mon, Sep 08, 2008 at 03:24:58PM +0800, Zhu Yi wrote:
> >
> >> I find the wireless-testing GIT has been rebased twice in less than one
> >> month. Does it mean you give up making it a long lived merge-able tree?
> >> This may affect to the downstream wireless drivers code management. At
> >> least for iwlwifi, we'd expect to merge with wireless-testing everytime.
> >
> > There must be some mistake, it has not been rebased at all -- at
> > least not as far as git is concerned.  I have done my now customary
> > "revert everything, pull from Linus re-apply" thing that I call a
> > virtual rebase, but the history has remained continuous.
> >
> > The non-master branches do get rebased of course.  Perhaps you saw
> > that and thought that master had been rebased as well?
> 
> FWIW, I also have had conflicts while pulling wireless-testing#master
> and I similarly thought that you have rebased it. But if you didn't I
> don't know what happened.

It is possible that I mistakenly copied the wrong tree out there or
something like that -- it has happened occasionally.  Generally I know
when I've done that and correct it immediately, but it is possible
that it happened and the wrong tree was sitting under wireless-testing
for a day or two.  If so, then I apologize.

John

      reply	other threads:[~2008-09-09 14:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-08  7:24 wireless-testing rebased again? Zhu Yi
2008-09-08 14:21 ` John W. Linville
2008-09-09  5:47   ` Kalle Valo
2008-09-09 14:05     ` John W. Linville [this message]

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=20080909140556.GA4291@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=kalle.valo@nokia.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=yi.zhu@intel.com \
    /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.