Remove git lfs clone command from man#3301
Conversation
PastelMobileSuit
left a comment
There was a problem hiding this comment.
Thanks for putting this together, it looks great! ✨
If you want to remove git lfs checkout as well I'm all for that, as that's also been deprecated! @ttaylorr are you on-board with that change as well?
|
Thanks @PastelMobileSuit! I've also removed |
git lfs clone command from man|
If you want to remove `git lfs checkout` as well I'm all for that, as
that's also been deprecated! @ttaylorr are you on-board with that
change as well?
I don't think that we should remove 'git lfs checkout' in the same way
that you have removed 'git lfs clone' here.
It's known that we won't be adding any new features or supporting 'git
lfs clone' in the future, but @bk2204 has just made some improvements,
and marked the command as no longer deprecated in 35ba22d (docs: add
--to and related options to docs, 2018-10-02).
That all said, I think that what you've got here looks great. I think
that all of:
$ git lfs clone --help
$ git lfs help clone
$ man git-lfs-clone
should still work, and the way that you've made the changes here ensures
that that is the case. This'll allow users to learn about the 'git lfs
clone' command between now and the time that we remove it from the
client (circa v3.0.0), should they need it for any exotic reason.
Eventually, we'll remove the clone command entirely (and thusly drop its
manpage, too), but I think that this is the right change for now.
|
|
@ttaylorr let me know if you're ok with this. Otherwise I can revert
the adittional change.
Can you please drop this change (instead of reverting it, so as not to
add additional commits to the history)? Thank you!
|
f5a42ec to
67723dd
Compare
git lfs clone command from man
|
@ttaylorr thanks for the meticulous response. Yes, all git-lfs/commands/command_checkout.go Lines 38 to 44 in b8f9b11
I shouldn't have used the word revert in this repository because I actually meant to say remove or even better reset --hard. I've dropped the change and updated the pull request title. 😅 |
|
However, should we remove the `WARNING` message or the whole `msg` in
the following part?
https://github.com/git-lfs/git-lfs/blob/b8f9b11a2a55289fb77418fef87fa98b04d66510/commands/command_checkout.go#L38-L44
@bk2204 can you take a look at this?
|
|
@gtsiolis Thanks again for your wonderful contribution! |
|
Thanks @ttaylorr @PastelMobileSuit! 🍉 |
|
Sure. I'll put in a pull request to undeprecate it. |
|
@bk2204 I've pushed some changes in gtsiolis@a411779. Let me know if you think this is ok to submit a pull request. If this is more complex than this, feel free to take this over. I've also noticed the |
|
No problem @bk2204! I'm glad we made identical changes. |
@bk2204 what do you think of this? |
|
I think as long as the command itself still exists, it would be better to keep the test for the deprecated message. Of course, when we remove the command in v3.0.0, we can remove the test for the deprecated warning. |
|
@bk2204 you're right, I completely forgot the command is still there. 😅 |
|
Not a problem. Glad you're thinking about ways to keep things tidy. |
|
Apologies if this is inappropriate to 'hijack' the PR, but I think this is very related. Given that
is this suggestion from the Tutorial still valid or should it be updated as well?
Perhaps, for common users, the recommended way to install-configure-clone is simply to:
Then, no more fiddling with |
Ah, this should certainly be updated. |
|
I've fixed that text so it's now accurate. Thanks for pointing it out! |
|
Thank you! |
The warning you get when you run
git lfs cloneis a bit misleading (see 47fa852#r30762174). This will remove thegit lfs clonecommand fromman(see 47fa852#r30753241). @PastelMobileSuit could you review this? 🍄