From: Blu Corater <blu@daga.cl>
To: git <git@vger.kernel.org>
Subject: Re: replacing a bad commit
Date: Mon, 5 Feb 2007 17:21:54 -0300 [thread overview]
Message-ID: <20070205202154.GA21890@daga.cl> (raw)
In-Reply-To: <20070205200236.GB8623@spearce.org>
On Mon, Feb 05, 2007 at 03:02:36PM -0500, Shawn O. Pearce wrote:
[...]
> The faster you abandon the idea of branch tip as argument, the
> faster you will pickup the more advanced operations in Git.
[...]
Indeed. Changing that piece of mindframe makes git look a lot more
powerful than it already was in my mind.
Thanks.
--
Blu.
next prev parent reply other threads:[~2007-02-05 20:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 15:39 replacing a bad commit Blu Corater
2007-02-05 16:38 ` Jakub Narebski
2007-02-05 19:53 ` Blu Corater
2007-02-05 20:02 ` Shawn O. Pearce
2007-02-05 20:21 ` Blu Corater [this message]
2007-02-05 20:38 ` Jakub Narebski
2007-02-05 20:53 ` Blu Corater
2007-02-05 20:58 ` Shawn O. Pearce
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=20070205202154.GA21890@daga.cl \
--to=blu@daga.cl \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.