cli internals: split jj git subcommand into separate files
#3896
Conversation
|
I vote against this move, but I don't have strong feeling. If people agree, I'm file with this change. BTW, we can also inline |
Why are you against it? Which editor do you use? I'm curious if the choice of editor impacts a person's preference here. I use VS Code which makes it quite easy to open a file by name or by contents. Maybe that's harder with some editors (it certainly is for me when using Emacs or Vim but that's probably mostly because I've never bothered to learn either of them). |
Emacs ;)
Yeah, that's probably it. I personally find it's easier to read/search/edit in one file of reasonable size than opening multiple small related files. That's the same reason that editing multiple commit descriptions in one buffer is easier. |
fowles
changed the title
git remote subcommand into separate filesgit remote subcommand into separate files
Moved commands are `git clone`, `git export`, `git fetch`, `git import`, `git init`, `git push`, `git remote`, and `git submodule`.
fowles
changed the title
git remote subcommand into separate filesjj git subcommand into separate files
There was a problem hiding this comment.
Quoting @yuja:
I vote against this move, but I don't have strong feeling. If people agree, I'm file with this change.
It sounded on Discord like no one has really strong opinions. There we were more people for than against, so I think we should merge this.
For the record, @fowles and I work for the same company, but I'll approve this anyway since it seems clearly not specific to Google's interests.
No description provided.