[MonoDevelop] Git add-in
taktaktaktaktaktaktaktaktaktak at gmail.com
Thu Jul 29 10:42:53 EDT 2010
>> If you are concerned about the Checkout command, which has a special
>> meaning in git, we can change the name and use something more explicit
>> like "Get Project from Repository" or something like that.
> OK, as long as there is a way to segregate the commands. I think changing
> the checkout command will be beneficial and will cause less confusion.
In my opinion, it's more important to map the same commands to the
same(-ish) actions across the board in MonoDevelop than anything else.
So "Checkout" should either be disabled or mapped to `git clone`, but
not to `git checkout`
Please don't rename Checkout to something vague, since some VCSs (e.g.
bzr) support both the concept of a svn-style checkout and a git-style
>> I disagree with that point of view. The goal of an IDE is to simplify
>> the development process. If we replicate every single git command, we
>> are not simplifying, we are exposing all the complexity of git.
>> As a user I don't want to have to deal with the complexity of git every
>> day. There are only a few commands I need to use in everyday work
>> (review changes, commit changes, update from repo). I want MD to take
>> the correct decisions for me in order to perform those operations with
>> git. In case I need to do more advanced git operations, I can always
>> open a console and use the git command.
I agree completely.
> I agree in simplifying the workflow with Git, but at the same time we need
> to stay uniform with the naming in some way. I have yet to see an IDE
> that supports Git not do the same thing.
Again, I feel like it's far more important to keep the naming
consistent within MD than between MD and Git.
Would it be useful to have a DVCS abstraction that adds things common
to the major DVCSs (bzr, git, hg)? (clone, pull, push, merge, ...)
Or is the perspective of each of those too different for a useful
amount of abstraction?
More information about the Monodevelop-list