git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to re-use setups in multiple tests?

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Oct 1, 2007, 12:39 UTC
Message-ID
<Pine.LNX.4.64.0710011336530.28395@racer.site>
In-Reply-To
<550f9510710010516s305c843br53da294f65318862@mail.gmail.com>
Hi,
On Mon, 1 Oct 2007, Tom Clarke wrote:
Show 6 quoted lines
> In this case the first test rebases the branch created in setup (it's 
> testing the rebase merge strategy), the second test should do the same 
> thing, except check there is a warning if a --message option is passed.
> 
> 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.

Ciao, Dscho

Previous: Tom ClarkeNext: Tom Clarke
Message 4 of 6 in “How to re-use setups in multiple tests?”
  1. Tom ClarkeOct 1, 2007
  2. Johannes SchindelinOct 1, 2007
  3. Tom ClarkeOct 1, 2007
  4. Johannes SchindelinOct 1, 2007
  5. Tom ClarkeOct 1, 2007
  6. Karl HasselströmOct 1, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.