[PATCH v3] commit: amending with --close-branch (issue3445)

[Iulian Stana]

I think that I didn't understand clearly the idea....
You said that there is a problem with 'hg init, does this mean that I must
put my test on the file without
using  'hg init' ? Is this all that I have to do or there is anything else
that I must do for this bug?


Iulian



2013/5/10 Kevin Bullock <kbullock+mercurial at ringworld.org>

> On 7 May 2013, at 4:05 PM, Iulian Stana wrote:
>
> > # HG changeset patch
> > # User Iulian Stana <julian.stana at gmail.com>
> > # Date 1367512607 -10800
> > #      Thu May 02 19:36:47 2013 +0300
> > # Branch stable
> > # Node ID 77cd996405eeade9d0b2b9a2293126c8fcbf1da0
> > # Parent  90f4587801ed6c525d1264d8f5b9285fb5cb71cc
> > commit: amending with --close-branch (issue3445)
>
> This looks mostly unchanged from V2, aside from adding too many tests in
> test-commit-amend.t instead of test-commit.t.
>
> Read this: <
> http://mercurial.selenic.com/wiki/WritingTests#No_more_new_test_scripts.21
> >
>
> And note that pretty much any time you reach for an 'hg init' in a test,
> that qualifies as "adding a completely new test".
>
> pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
> Kevin R. Bullock
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20130513/1f7cf33e/attachment.html>