Found 230 matching messages (0.136 seconds). Page 1 of 12.
... >> I still think that the GIT user interface sucks in many ways. The ... " does not automatically initiate network transfer). - "git merge" to merge another branch into ... willing to get rid of historical warts. Syntax of the command line arguments ...
git - Junio C Hamano - Nov 14 2006 - 18:36
... to get rid of historical warts. Syntax of the command > line ... scratch, using different prefix than > "git" (say "gu" that stands for ... of the discussion on UI warts doesn't exist in the ... anymore, despite its more user friendly interface - just because I didn ...
git - Alan Chandler - Nov 18 2006 - 03:59
... like "FETCH_HEAD" is something a user should really never have to ... checkout local-branch We're getting close to the desired functionality ... now, but the UI makes users cringe? "What's that : for ... a solution for UI warts in git. (If you would only ...
git - Carl Worth - Nov 16 2006 - 21:08
... to trip up new users in my experience. And what git does really well, (history exploring, allowing ... some specific workflow-oriented operations that git doesn't handle as well as ... But I don't think the user-interface for either of those operations ...
git - Carl Worth - Nov 15 2006 - 16:51
... Since then, having worked with git (the command-line program) exclusively ... think the benefits of new user interfaces are clear when they ... timing of my introduction to git contrasted with the timing of ... with dirty changes to a clean branch, do work there, and ...
git - Carl Worth - Nov 14 2006 - 16:56
... to get it pushed down into git > itself. > Agreed totally on the ... user base (in this case, they're using Subversion) on Git. ... a deal-killing "throw your hands up in disgust and give ... to paper over that particular wart. If there is a native ...
git - Steven Grimm - Nov 17 2006 - 16:30
... >> need the extreme power of git, Hg is simpler for people to ... wander up the git learning curve. > > My experience with the git user interface, for what it's worth, ... . Additionally this "complication" makes very clean model of repository - but you have ...
git - Jakub Narebski - Nov 24 2006 - 07:29
... little issues" are totally made up by > people > who had trouble ... Darcs, bzr and mercurial. With GIT, this is what happens [hanwen ... it does show the typical GIT user experience, at least mine ... how not to design a user-interface, try the above on ...
git - Han-Wen Nienhuys - Nov 16 2006 - 06:45
... it easier for occasional developers to keep a clean history, >>> and rebase and pull interfere badly. >> ... some implementation with warts http://thread.gmane.org/gmane.comp.version-control.git/30068 Message-Id: <20061025155009.GD5591@parisc-linux. ...
git - Jakub Narebski - Nov 17 2006 - 13:41
... thread. So I think we're better off just fixing the ... still think that the GIT user interface sucks in many ways ... the "remote-tracking branches" as user-visible branches possible for committing ... behavior?). When it improves the user experience, let's make the ...
git - Carl Worth - Nov 14 2006 - 17:10
... can be shipped with clear distinction between plumbing (i.e. git-update-index and friends) and porcelain (e.g. " ... that only fetches but with the user friendliness you outlined here), with backward compatibility wart to help old timers (e.g. "git pull" ...
git - Junio C Hamano - Nov 15 2006 - 01:35
... turned away by GIT's current user >> interface issues. The only ... to others. > > My complaints about git pull/fetch/push are by ... home page, trying to learn git). Mark - To unsubscribe from this ... list: send the line "unsubscribe git" in the body of a ...
git - Marko Macek - Nov 15 2006 - 15:05
... it less intimidating for new users. I just cannot do otherwise ... have a clear preference for GIT's _technology_, I still think ... still think that the GIT user interface sucks in many ways. ... branch by default. But having git-pull performing merges is IMHO ...
git - Nicolas Pitre - Nov 14 2006 - 16:52
... I think the benefits of new > > user interfaces are clear when they work ... the same degree of "authority" as git > Plumbing. ..snip passage about workflows.. Controversy's ... is the canonical workflow the _the_ Git porcelain supports (see the snipped ...
git - Petr Baudis - Nov 15 2006 - 00:08
... turned away by GIT's current user interface issues. The only ... is) total > braindamage. The native git branch naming convention is just ... would be implemented with a git-get command) which I think ... we probably could/should re-use the "git merge" name. The ...
git - Nicolas Pitre - Nov 15 2006 - 14:43
... were turned away by GIT's current user > interface issues. The only ... who see > value in the GIT technology but who would like to ... to others. My complaints about git pull/fetch/push are by ... whom I interact with through Git. They don't like pull/ ...
git - Shawn Pearce - Nov 15 2006 - 14:49
... I have to teach an interface notion: > > > > merge = pull . > > This is ... should basically ever use the "git merge" command > itself, not in ... the 'merge' command. I end up saying, "Oh, that's there ... That's nothing more than a user-interface trap for new ...
git - Carl Worth - Nov 15 2006 - 18:52
... in refs/{heads,tags}/ is looked up in remotes and if it's ... so heavily; and there are few warts here. But overally, I think this ... format but there're surely die-hard fans of Git's. (iv) ... issues. This is probably very subjective, but a blocker for me. ...
git - Petr Baudis - Nov 16 2006 - 01:12
... a simple and very straightforward user interface (the tools directly reflect ... to support distributed development model git has, while not taking full ... do so if they come up with a set of commands ... mostly works and quacks like git-fetch with set of tracking ...
git - Junio C Hamano - Nov 16 2006 - 06:31
... the "short"
> form.
>
> When you do
>
> git pull
git - Carl Worth - Nov 16 2006 - 13:01