From: Junio C Hamano <junkio@cox.net>
To: Kyle McMartin <kyle@parisc-linux.org>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] Move read_mostly definition to asm/cache.h
Date: Sun, 15 Jan 2006 01:48:02 -0800 [thread overview]
Message-ID: <7vu0c57rfx.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060112053618.GH25353@tachyon.int.mcmartin.ca> (Kyle McMartin's message of "Thu, 12 Jan 2006 00:36:18 -0500")
Kyle McMartin <kyle@parisc-linux.org> writes:
> Alternatively, if I had (I haven't touched the tree, just format-patch'd
> which looked right) used git-reset --hard HEAD and been up to date
> (working tree and index file) with whatever ended up being pointed
> to by HEAD, right?
Yes.
> I'll try to remember the symbolic-ref thing for next time, usually when
> this happens I just blow away the last commit and try again, but I felt
> adventurous today. :)
After making the mistake of committing to "master":
$ git commit ;# oops, to the master
$ git show-branch origin master read-mostly
! [origin] latest update from Linus
* [master] latest for read-mostly
--
* [master] latest for read-mostly
+* [origin] last update from Linus
you could do this, which would be easier to visualize:
$ git branch read-mostly ;# may need branch "-f" if exists.
$ git reset --hard HEAD^ ;# rewind the current head by one.
Which would give you this:
$ git show-branch origin master read-mostly
! [origin] latest update from Linus
* [master] latest update from Linus
! [read-mostly] latest for read-mostly
--
! [read-mostly] latest for read-mostly
+*! [origin] last update from Linus
prev parent reply other threads:[~2006-01-15 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-11 17:33 Kyle McMartin
2006-01-11 17:52 ` Linus Torvalds
2006-01-11 21:20 ` Junio C Hamano
2006-01-12 5:36 ` Kyle McMartin
2006-01-15 9:48 ` Junio C Hamano [this message]
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=7vu0c57rfx.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=kyle@parisc-linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®