Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Activity for ajv‭

Type On... Excerpt Status Date
Comment Post #283672 `git show-branch master topic^` is how I eventually dealt with the case I was facing, but as you say, that has its own issues. I do use `git log --oneline --graph --boundary master...topic` a lot, and that's often good enough, but for nontrivial histories it's hard to visually pick out which commits ...
(more)
over 2 years ago
Comment Post #283672 After experimenting a bit, it looks like I only run into a problem if the tip of one branch is a merge of the other. e.g. consider a history like this: ``` master *---*---A---B---* \ \ topic a---b---c---* ``` If I then do `git show-branch master topic`, it do...
(more)
over 2 years ago
Comment Post #283672 I did see --more, but I don't think it suits this use case. I'm not looking for 10 or 30 or 100 additional commits; I'm looking for "however many are needed to cover all commits that differ between the branches."
(more)
over 2 years ago
Comment Post #281160 Thanks. Not quite the answer I *wanted*, but exactly what I asked for.
(more)
about 3 years ago
Comment Post #281159 Edited for clarity and I'll add an example in a moment.
(more)
about 3 years ago
Comment Post #281159 YAML is my favored format, yes, but an ideal solution would be file-format-agnostic. E.g. python's dictconfig doesn't care what kind of file (if any) your input dict came from, as long as it has the right keys.
(more)
about 3 years ago
Comment Post #277485 Thanks. That makes sense, though the choice of method still seems crazy to me. I would think it would be simpler -- and definitely clearer -- to cast it to date and then cast back to DT. (or just...not cast it back and use the date as is. The difference wasn't important in-context)
(more)
over 3 years ago