Bit – A modernized Git CLI written in Go • Hacker News Board

Re: Bit – A modernized Git CLI written in Go

#111

Post by pdsOne » Mon, Oct 12, 2020, 3:59 PM UTC

ryukafalz wrote: post #85

torben-friis wrote: post #80

Earlier quoted context omitted.

My team doesn't write long format commit messages and it's never been an issue. When we need to track down changes we use the corresponding mr, which includes a description as well as a link to the relevant cards. I personally like this format more because it lets you both be "dirty" in your branch writing commits for yourself, and not have to use amends/rebasing. I can see how it would be annoying for someone that d…

If you ever switch from Gitlab to another git host, you’ll lose all that history though. Maybe you’re fine with that, but I wouldn’t be.

Unrelated question but why don't more people use Gerrit instead of Gitlab or Github? To me Gerrit flow makes the most sense.

Re: Bit – A modernized Git CLI written in Go

#112

Post by sethammons » Mon, Oct 12, 2020, 4:04 PM UTC

stinos wrote: post #27

Honest question: what's up with the (2 hours ago) notation? I've seen this before in a couple of git-related and other applications but personally never understood why one would pick this over date/hour. Is this a cultural thing? Do some people actually find this better (from the point of conveying timestamp information)? My main problem with it, apart from not having a high resolution, is that it usually just leads…

I hate it. “17 days ago” - yeah, thanks, now let me manually figure out _when_ that was. I can see how some folks would like “30 minutes ago” but why not give both (a timestamp and relative offset)?

Re: Bit – A modernized Git CLI written in Go

#113

Post by juped » Mon, Oct 12, 2020, 4:09 PM UTC

raimue wrote: post #69

OJFord wrote: post #48

I really liked the look of this, until I got to `save`/`sync` in the readme... That's not how I want to work, and it's not how I want other people to work in a repository I'm using. I know 'I don't have to use them then I can just use the git subcommands', but that's not the point, it's a big signal ('90% of the time the above commands will have you covered.') about the motivation/angle/philosophy of the project that…

The save command also accepts the commit message on command line only instead of opening an editor. I do not understand how people can live with only a single line for the commit message. For a new feature, I need to provide some details what is added and how it can be used. For a bugfix, a single line is rarely enough to describe the problem, what you changed, and why this change solves the problem. Writing good com…

Most people don't really use version control, they just use version control programs because they've been told they're supposed to. They might as well be using rsync.

Most of them would benefit from learning to actually use it, but this is unfortunately niche.

Re: Bit – A modernized Git CLI written in Go

#114

Post by [deleted] » Mon, Oct 12, 2020, 4:16 PM UTC

[deleted]

Re: Bit – A modernized Git CLI written in Go

#115

Post by ljm » Mon, Oct 12, 2020, 4:25 PM UTC

user5994461 wrote: post #93

ljm wrote: post #91

Earlier quoted context omitted.

I have to say that the level of confidence you have while being so misinformed is rather comical. I lived in Greenwich, I don't remember entering a new space-time continuum when getting off the DLR at Cutty Sark. You know, compasses spinning eratically, GPS going haywire, cuckoo clocks spinning out of control, because the bubble around the Greenwich Meridian transcends the mortal plane. GMT is the timezone we have be…

See, you agree that Greenwich is not under GMT time half of the year. That's all I am saying. You don't have to resort to name calling.

Not really, it's just an utterly absurd thing to hang up on. Did you know that Greenwich, NY is also never under GMT for the whole year?

Re: Bit – A modernized Git CLI written in Go

#116

Post by brandmeyer » Mon, Oct 12, 2020, 4:34 PM UTC

pdsOne wrote: post #111

ryukafalz wrote: post #85

Earlier quoted context omitted.

If you ever switch from Gitlab to another git host, you’ll lose all that history though. Maybe you’re fine with that, but I wouldn’t be.

Unrelated question but why don't more people use Gerrit instead of Gitlab or Github? To me Gerrit flow makes the most sense.

Speaking only for myself: Because Gerrit's unit of review is a single commit instead of a branch. Commits are units of change, but the unit of work and review is almost always a series of related changes. Just because the changes are individually atomic (testable, cherry-pickable, etc) doesn't mean that I want to review them that way. The typical flow is for an engineer to produce a cluster of inter-related changes that motivate and rationalize each other.

Reviewing such a chunk in Gerrit is a PITA. It breaks up the flow of discussion and encourages a myopic perspective on the work.

Re: Bit – A modernized Git CLI written in Go

#117

Post by s_dev » Mon, Oct 12, 2020, 4:34 PM UTC

chriswalz wrote: post #2

Git is an awesome tool – so awesome that it has a vast plethora of options and commands to do just about anything. Bit attempts to alleviate some of that pain.

Got would have been a better name.

It includes Go and sounds like Git.

Re: Bit – A modernized Git CLI written in Go

#118

Post by zie » Mon, Oct 12, 2020, 4:37 PM UTC

sethammons wrote: post #112

stinos wrote: post #27

Honest question: what's up with the (2 hours ago) notation? I've seen this before in a couple of git-related and other applications but personally never understood why one would pick this over date/hour. Is this a cultural thing? Do some people actually find this better (from the point of conveying timestamp information)? My main problem with it, apart from not having a high resolution, is that it usually just leads…

I hate it. “17 days ago” - yeah, thanks, now let me manually figure out _when_ that was. I can see how some folks would like “30 minutes ago” but why not give both (a timestamp and relative offset)?

My thinking: The actual timestamp should be in a tooltip/hover if you are going to default to relative dates like this.

Re: Bit – A modernized Git CLI written in Go

#119

Post by donio » Mon, Oct 12, 2020, 4:53 PM UTC

zie wrote: post #118

sethammons wrote: post #112

Earlier quoted context omitted.

I hate it. “17 days ago” - yeah, thanks, now let me manually figure out _when_ that was. I can see how some folks would like “30 minutes ago” but why not give both (a timestamp and relative offset)?

My thinking: The actual timestamp should be in a tooltip/hover if you are going to default to relative dates like this.

Even then it's wasting my time. The "17 days ago" is basically never what I want.

Re: Bit – A modernized Git CLI written in Go

#120

Post by amelius » Mon, Oct 12, 2020, 5:30 PM UTC

stinos wrote: post #27

Honest question: what's up with the (2 hours ago) notation? I've seen this before in a couple of git-related and other applications but personally never understood why one would pick this over date/hour. Is this a cultural thing? Do some people actually find this better (from the point of conveying timestamp information)? My main problem with it, apart from not having a high resolution, is that it usually just leads…

It's especially frustrating when you need to compare two timestamps.

The problem also exists on HN. For example, in a discussion you might want to check who said something first. But if both comments say "3 days ago", then that's kinda difficult (unless you want to wait until one of them flips to 4 days ago).