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

Re: [PATCH 1/7] Add a minimal test for git-cherry

From
Yann Dirson <ydirson@altern.org>
Date
Jan 8, 2006, 09:58 UTC
Message-ID
<20060108095843.GD32585@nowhere.earth>
In-Reply-To
<7vy81r5ugx.fsf@assigned-by-dhcp.cox.net>
On Sat, Jan 07, 2006 at 06:22:54PM -0800, Junio C Hamano wrote:
Show 18 quoted lines
> Yann Dirson <ydirson@altern.org> writes:
> 
> > This test checks that git-cherry finds the expected number of patches
> > in two simple cases.
> >
> > Signed-off-by: Yann Dirson <ydirson@altern.org>
> >
> > +test_expect_success \
> > +    'cherry-pick one of the 2 patches, and check cherry recognized one and only one as new' \
> > +    'git-cherry-pick my-topic-branch^0 &&
> > +     echo $(git-cherry master my-topic-branch) &&
> > +     expr "$(echo $(git-cherry master my-topic-branch) )" : "+ [^ ]* - .*"
> > +'
> 
> I wonder if "+ followed by -" order is stable here.  If you make
> commits in the my-topic-branch fast enough, they would get the
> same timestamp and I suspect the order from rev-list would be
> left to chance.

We could maybe insert a sleep between the two commits ? Not that I find it too appealing, however...

-- 
Yann Dirson    <ydirson@altern.org> |
Debian-related: <dirson@debian.org> |   Support Debian GNU/Linux:
                                    |  Freedom, Power, Stability, Gratis
     http://ydirson.free.fr/        | Check <http://www.debian.org/>
Previous: Junio C Hamano
Message 3 of 3 in “Add a minimal test for git-cherry”
  1. 1/7 Add a minimal test for git-cherryYann Dirson, Jan 8, 2006
  2. Junio C HamanoJan 8, 2006
  3. Yann DirsonJan 8, 2006

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.