From: Rob Landley <rob@landley.net>
To: Pavel Machek <pavel@suse.cz>
Cc: Roman Zippel <zippel@linux-m68k.org>,
linux-kernel@vger.kernel.org, Sam Ravnborg <sam@ravnborg.org>
Subject: Re: [PATCH] make miniconfig (take 2)
Date: Mon, 21 Nov 2005 23:14:39 -0600 [thread overview]
Message-ID: <200511212314.41605.rob@landley.net> (raw)
In-Reply-To: <20051121192431.GJ29518@elf.ucw.cz>
On Monday 21 November 2005 13:24, Pavel Machek wrote:
> Hi!
> > I'm hoping to get an ack from the kconfig guys first, hence the cc:
> >
> > But does it work ok for you?
>
> I was not even able to patch it properly :-(. Version against current
> -git would be handy.
Ouch. It applied cleanly against both -rc1 and -rc2. Ok, um...
Is there any way to extract a current patch against 2.6.15-rc1-git1 from the
git web page? I can get the most _recent_ diff at:
http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git
But that's just for one changeset. Possibly I can iterate through the
changesets to get all the diffs back to -git1 and apply them in sequence (if
that works). But the ability to right click and download one big rollup
patch would be really really nice.
Rob
P.S. I don't use git. Poked at it a few times, but I made the mistake of
reading largeish chunks of the git man page and the git glossary in an
attempt to get up to speed, and got a headache. Anything that can define
"clean" in such a way that I'm _less_ sure of the definition afterwards:
http://www.kernel.org/pub/software/scm/git/docs/glossary.html
Learning git went back on the to-do list somewhere between cleaning behind the
refrigerator and sorting my book collection by author...
next prev parent reply other threads:[~2005-11-22 5:15 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-17 12:29 Quick and dirty miniconfig howto, with feature suggestions Rob Landley
2005-11-20 3:08 ` Roman Zippel
2005-11-20 5:54 ` Rob Landley
2005-11-21 6:15 ` [PATCH] make miniconfig Rob Landley
2005-11-21 16:06 ` [PATCH] make miniconfig (take 2) Rob Landley
2005-11-21 17:26 ` Pavel Machek
2005-11-21 17:46 ` Rob Landley
2005-11-21 17:36 ` Pavel Machek
2005-11-21 17:50 ` Rob Landley
2005-11-21 18:28 ` Pavel Machek
2005-11-21 18:53 ` Rob Landley
2005-11-21 19:24 ` Pavel Machek
2005-11-22 5:14 ` Rob Landley [this message]
2005-11-22 22:54 ` Pavel Machek
2005-11-23 8:58 ` Rob Landley
2005-11-23 13:21 ` Pavel Machek
2005-11-24 3:19 ` Rob Landley
2005-11-25 19:45 ` Pavel Machek
2005-11-25 21:45 ` Rob Landley
2005-11-25 22:09 ` Pavel Machek
2005-11-25 22:20 ` Rob Landley
2005-11-26 2:34 ` Kyle Moffett
2005-11-26 12:25 ` Rob Landley
2005-11-26 14:19 ` Pavel Machek
2005-11-26 15:51 ` Rob Landley
2005-11-24 4:02 ` Rob Landley
2005-11-25 19:46 ` Pavel Machek
2005-11-26 1:53 ` Andre Noll
2005-11-22 5:17 ` Rob Landley
2005-11-24 13:56 ` Roman Zippel
2005-11-24 17:45 ` Rob Landley
2005-11-25 1:48 ` Roman Zippel
2005-11-25 8:18 ` Rob Landley
2005-11-25 15:02 ` Roman Zippel
2005-11-25 16:47 ` Rob Landley
2005-11-25 21:12 ` Rob Landley
2005-11-27 23:20 ` Roman Zippel
2005-11-28 0:59 ` Rob Landley
2005-11-29 1:00 ` Roman Zippel
2005-11-29 2:26 ` Rob Landley
2005-11-30 2:29 ` Roman Zippel
2005-11-20 3:25 ` Quick and dirty miniconfig howto, with feature suggestions Rob Landley
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=200511212314.41605.rob@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome