public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Nico -telmich- Schottelius <nico-linux-next@schottelius•org>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org
Subject: Re: linux-next: Tree for August 4
Date: Mon, 4 Aug 2008 11:51:49 +0200	[thread overview]
Message-ID: <20080804095149.GC4747@denkbrett.schottelius.org> (raw)
In-Reply-To: <20080804162924.f3c5c3d4.sfr@canb.auug.org.au>

[-- Attachment #1: Type: text/plain, Size: 991 bytes --]

Good morning!

Stephen Rothwell [Mon, Aug 04, 2008 at 04:29:24PM +1000]:
> Changes since next-20080801:
 
I am currently trying to make linux-next a bit more debug-friendly
and merge your tree from time to time.

Thus I do:

   git-merge linux-next/master
   git-checkout linux-next/master $(git-ls-files --unmerged | awk '{ print $4 }')
   git-add $(git-ls-files --unmerged | awk '{ print $4 }')
   git-commit

The result can now be found at

   http://unix.schottelius.org/cgi-bin/gitweb.cgi?p=foreign/linux-2.6

respectively

   http://unix.schottelius.org/git/foreign/linux-2.6/

I'll use the merged result for testing linux-next, perhaps adding
other branches later to test which branches you merge from are
directly mergable, without the need for a rebase.

Sincerly,

Nico

-- 
Think about Free and Open Source Software (FOSS).
http://nico.schottelius.org/documentations/foss/the-term-foss/

PGP: BFE4 C736 ABE5 406F 8F42  F7CF B8BE F92A 9885 188C

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

next prev parent reply	other threads:[~2008-08-04  9:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-04  6:29 linux-next: Tree for August 4 Stephen Rothwell
2008-08-04  9:51 ` Nico -telmich- Schottelius [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-08-04  8:01 Stephen Rothwell
2010-08-04  5: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=20080804095149.GC4747@denkbrett.schottelius.org \
    --to=nico-linux-next@schottelius$(echo .)org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox