LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: linux-next: Tree for March 6
Date: Fri, 6 Mar 2009 11:24:50 -0800	[thread overview]
Message-ID: <20090306112450.12901a19.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090306191311.697e7b97.sfr@canb.auug.org.au>

On Fri, 6 Mar 2009 19:13:11 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> Dropped trees (temporary):
> 	rr (build problem)

It's quite irritating and somewhat risky when this happens.  It means
that I have to teporarily drop or rework patches to fix things up. 
Then the patch needs to be undropped or unreworked when the offending
tree gets restored.

Is it possible to just drop back to the previous day's version when
something gets screwed up?


  parent reply	other threads:[~2009-03-06 19:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-06  8:13 Stephen Rothwell
2009-03-06 19:01 ` linux-next: Tree for March 6 (ath9k) Randy Dunlap
2009-03-06 19:35   ` Gabor Juhos
2009-03-06 19:41     ` Randy Dunlap
2009-03-06 19:40       ` John W. Linville
2009-03-11 17:19         ` Randy Dunlap
2009-03-11 18:19           ` John W. Linville
2009-03-06 19:24 ` Andrew Morton [this message]
2009-03-10  5:47   ` linux-next: Tree for March 6 Stephen Rothwell
2009-03-06 21:24 ` [PATCH -next] dvb/frontends: fix duplicate 'debug' symbol Randy Dunlap
2009-03-06 23:59   ` Andrew Morton
2009-03-07  0:05     ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2008-03-06  5:26 linux-next: Tree for March 6 Stephen Rothwell
2008-03-06  9:07 ` Andy Whitcroft
2008-03-06 11:50   ` Stephen Rothwell
2008-03-07  2:10     ` Stephen Rothwell

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=20090306112450.12901a19.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --subject='Re: linux-next: Tree for March 6' \
    /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

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).