Skip to content
New issue

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

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

Already on GitHub? # to your account

revision range for titan log #50

Open
CloudSurgeon opened this issue Oct 2, 2019 · 1 comment
Open

revision range for titan log #50

CloudSurgeon opened this issue Oct 2, 2019 · 1 comment
Labels
Priority: Normal Issues to be address during sprint Type: Feature New feature or request

Comments

@CloudSurgeon
Copy link
Contributor

CloudSurgeon commented Oct 2, 2019

Problem

Be able to list titan commits between a certain range

Solution

Show only commits in the specified revision range. When no is specified, it defaults to all. ie titan log -1 ugdemo would only show the most recent commit.

Alternatives

Do nothing and use some complex awk/sed combo
this shell oneliner returns the last commit titan log ugdemo | sed '/commit/h; $!d; x'| awk '{print $2}'

@CloudSurgeon CloudSurgeon added the Type: Feature New feature or request label Oct 2, 2019
@eschrock
Copy link
Contributor

eschrock commented Oct 2, 2019

Definitely have wanted something in this vein. The full suite of "commit limiting" features in 'git log' is mind-boggling:

https://git-scm.com/docs/git-log#_commit_limiting

We should pick a few basic ones to implement at first. Our CLI options framework may not like the "-1" style, but that is definitely what people are used to with git.

@mcred mcred changed the title revision range for git log revision range for titan log Oct 3, 2019
@mcred mcred added Priority: Normal Issues to be address during sprint Type: Feature New feature or request and removed Type: Feature New feature or request labels Oct 3, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Priority: Normal Issues to be address during sprint Type: Feature New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants