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

Re: [PATCH 2/2] t3401: use test_commit in setup

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Dec 9, 2011, 19:02 UTC
Message-ID
<CALkWK0k-dL3xZ+dyqdACj7man-Q2QrAPZCCMhXiX0WNGZHv6Fw@mail.gmail.com>
In-Reply-To
<1323449952-14161-2-git-send-email-martin.von.zweigbergk@gmail.com>
Hi again,
Martin von Zweigbergk wrote:
Show 5 quoted lines
> Simplify t3401 by using test_commit in the setup. This lets us refer
> to commits using their tags and there is no longer a need to create
> the branch my-topic-branch-merge. Also, the branch master-merge points
> to the same commit as master (even before this change), so that branch
> does not need to be created either.

The terms "tag" and "branch" here have no significance, so de-emphasizing them to "ref" is probably a good idea. Isn't the truth more like: instead of creating commits and creating refs to track those commits by hand, use test_commit to achieve the same result in a single step?

Cheers.
-- Ram
Previous: Martin von ZweigbergkNext: Jonathan Nieder
Message 3 of 7 in “t3401: modernize style”
  1. 1/2 t3401: modernize styleMartin von Zweigbergk, Dec 9, 2011
  2. 2/2 t3401: use test_commit in setupMartin von Zweigbergk, Dec 9, 2011
  3. Ramkumar RamachandraDec 9, 2011
  4. Jonathan NiederDec 9, 2011
  5. Ramkumar RamachandraDec 9, 2011
  6. Jonathan NiederDec 9, 2011
  7. Martin von ZweigbergkDec 10, 2011

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.