From: Junio C Hamano <junkio@cox.net>
To: Jon Loeliger <jdl@freescale.com>
Cc: git@vger.kernel.org
Subject: Re: Now What?
Date: Sun, 06 Nov 2005 12:33:18 -0800 [thread overview]
Message-ID: <7vr79twm7l.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1131043869.10979.17.camel@cashmere.sps.mot.com> (Jon Loeliger's message of "Thu, 03 Nov 2005 12:51:10 -0600")
Jon Loeliger <jdl@freescale.com> writes:
> On Wed, 2005-11-02 at 19:43, Chris Shoemaker wrote:
>
> .... Also,
> I was annoyed that "git revert -n commit-name" created
> conflicts and the reversal and merges didn't happen
> for me cleanly even though they did for Junio.
>
> So either I don't get it, or it isn't working quite
> right these days. Not sure. Advice sought.
It's been a while since I used git-revert the last time. I
should find time to run the examples myself.
> Reversing Commits
> -----------------
> While a goal of a revision control system is to record
> ...
The flow-chart based recipe is wonderful.
next prev parent reply other threads:[~2005-11-06 20:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 1:30 Now What? Jon Loeliger
2005-11-03 1:43 ` Chris Shoemaker
2005-11-03 9:00 ` Junio C Hamano
2005-11-03 18:51 ` Jon Loeliger
2005-11-06 20:33 ` Junio C Hamano [this message]
2005-11-03 8:38 ` Peter Eriksen
2005-11-03 10:00 ` Junio C Hamano
2005-11-03 17:05 ` Daniel Barkalow
2005-11-03 17:27 ` Linus Torvalds
2005-11-03 18:38 ` Junio C Hamano
2005-11-03 17:30 ` Peter Eriksen
2005-11-03 22:07 ` Junio C Hamano
2005-11-03 22:33 ` Josef Weidendorfer
2005-11-04 17:06 ` Daniel Barkalow
2005-11-03 17:25 ` Linus Torvalds
2005-11-03 8:58 ` Junio C Hamano
2005-11-03 20:55 ` Junio C Hamano
2005-11-03 22:17 ` Josef Weidendorfer
2005-11-03 22:51 ` Junio C Hamano
2005-11-03 23:26 ` Josef Weidendorfer
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=7vr79twm7l.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=jdl@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).