Skip to content
This repository has been archived by the owner on Jan 20, 2018. It is now read-only.

.topmsg should be optional #39

Open
aspiers opened this issue Feb 9, 2015 · 0 comments
Open

.topmsg should be optional #39

aspiers opened this issue Feb 9, 2015 · 0 comments

Comments

@aspiers
Copy link

aspiers commented Feb 9, 2015

It's often too heavyweight to expect the user to write a .topmsg file; the combination of the topic branch name and the log messages for the "real" commits within that topic branch are often sufficient, especially when the topic branch only contains a single "real" commit.

That said, it's worthwhile keeping the functionality as long as it's optional - having a message which summarises the topic branch can be very useful when sharing more complex topic branches, and also for auto-generating patch series cover letters and github pull requests.

See also #38, in which I propose ditching the .topmsg file altogether.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant