From: "Tom Clarke" <tom@u2i.com>
To: "Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: How to re-use setups in multiple tests?
Date: Mon, 1 Oct 2007 14:46:46 +0200 [thread overview]
Message-ID: <550f9510710010546q55209759k4770cd3e78121cfc@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0710011336530.28395@racer.site>
On 10/1/07, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > I suppose I could find the old pre-rebase head and work with that, but
> > that doesn't seem that clean to me.
>
> You can use "git reset --hard master@{1}", and it really escapes me why
> this should not be clean, and why you want to jump through hoops instead
> using a much more complicated technique.
That'll be because my git knowledge isn't good enough to make it
clean. Thanks for the suggestion :-)
-Tom
next prev parent reply other threads:[~2007-10-01 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 10:27 How to re-use setups in multiple tests? Tom Clarke
2007-10-01 11:45 ` Johannes Schindelin
2007-10-01 12:16 ` Tom Clarke
2007-10-01 12:39 ` Johannes Schindelin
2007-10-01 12:46 ` Tom Clarke [this message]
2007-10-01 13:40 ` Karl Hasselström
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=550f9510710010546q55209759k4770cd3e78121cfc@mail.gmail.com \
--to=tom@u2i.com \
--cc=Johannes.Schindelin@gmx.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.
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).