From: Ralf Baechle <ralf@linux-mips.org>
To: linux-mips@linux-mips.org
Subject: Git stuff
Date: Mon, 11 Dec 2006 15:53:41 +0000 [thread overview]
Message-ID: <20061211155341.GA3542@linux-mips.org> (raw)
I've been asked what that strange commit
commit e81fbbbb9a0d8072460c223e935fb1aca4231dc0
Merge: 6f0b1e5... 9202f32...
Author: Ralf Baechle <ralf@linux-mips.org>
Date: Mon Dec 11 12:25:29 2006 +0000
Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torva
nothing to commit
from around noon today means - it's a merge commit where after resolution
of the merge conflict there was nothing left to commit. Nothing to worry :)
Also sorry for the flood of commit messages. I cherry pick any commit
that is a fix to the -stable branches which ends multiplying the number
of commits. If you only care about certain branches you can use i.e.
procmail to filter away the uninterestin messages. The format of the
mail messages was choosen to make that easy.
Ralf
reply other threads:[~2006-12-11 15:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20061211155341.GA3542@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.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