Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fcm merge --auto-log: empty lines on merging auto-logged branch #232

Open
benfitzpatrick opened this issue Jul 26, 2016 · 0 comments
Open
Labels
Milestone

Comments

@benfitzpatrick
Copy link
Contributor

If the trunk is merged into a branch with fcm merge --auto-log and then later the branch is merged
back, again using --auto-log, empty entries will appear where the trunk merge revision autolog entries should be.

For example, with a branch with this log message:

------------------------------------------------------------------------
r5 | ben | 2016-07-26 09:22:28 +0100 (Tue, 26 Jul 2016) | 6 lines

Merged into /branches/dev/ben/r1_branchy: /trunk@3 cf. /trunk@1
----
r3:
> Add foo
----

a later merge of this branch back to the trunk can give:

------------------------------------------------------------------------
r7 | bfitz | 2016-07-26 09:28:57 +0100 (Tue, 26 Jul 2016) | 14 lines

Merge branch back
Merged into /trunk: /branches/dev/bfitz/r1_branchy@6 cf. /trunk@3
----
r6:
> Add bar
----
r5:
> ----
> ----
----
r4:
> Make new branch
----

------------------------------------------------------------------------

Where the auto-log message is long, this can give a lot of otherwise-empty 4-dash lines.

Noticed by @r-sharp.

@benfitzpatrick benfitzpatrick added this to the soon milestone Jul 26, 2016
@matthewrmshin matthewrmshin removed their assignment Sep 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants