From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: git@vger.kernel.org
Subject: Merging five months of Linux kernel history
Date: Sun, 29 Oct 2006 20:32:28 +0100 [thread overview]
Message-ID: <20061029193228.GR26271@lug-owl.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
Hi!
Due to a move to a new flat and other reasons, I wasn't able to
do daily merges from Linus's tree into our vax-linux tree.
My time situation has improved and I want to merge all the new
and shiny stuff, but it seems a straight "git pull" isn't the
best way to do that.
What I'd actually love to do is to go through all commits since the
last merge and pull/accept/cherry-pick then one by one. That way I'll
learn about new stuff. I'll specifically see generic changes that
imply arch-specific stuff, things I'll need to implement later on.
Is there any sane way to cluse such a large gap? I don't mind looking
through tenthousands of commits, as long as I get a chance to spot
"important" ones.
Thanks, JBG
--
Jan-Benedict Glaw jbglaw@lug-owl.de +49-172-7608481
Signature of: http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
the second :
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2006-10-29 19:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 19:32 Jan-Benedict Glaw [this message]
2006-10-29 20:34 ` Merging five months of Linux kernel history Junio C Hamano
2006-10-30 7:50 ` Jan-Benedict Glaw
2006-10-30 8:05 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061029193228.GR26271@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=git@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).