From: Lars Hjemli Date: Wed, 09 May 2007 20:38:26 GMT Subject: Re: [PATCH] checkout: allow full refnames for local branches Message-ID: <8c5c35580705091338r63acc7aaw43248ad246670e8b@mail.gmail.com> In-Reply-To: <20070509201105.GF3141@spearce.org> On 5/9/07, Shawn O. Pearce wrote: > Lars Hjemli wrote: > > On 5/9/07, Shawn O. Pearce wrote: > > >If you are building "porcelain" to sit over Git and offer up a pretty > > >view of things, I would encourage you to avoid the stock porcelain. > > >Don't use git-checkout, its stock porcelain. Instead go right to > > >the plumbing. The plumbing doesn't really change behavior as often > > >(if ever). > > > > Thanks, I probably will (also to avoid the shell scripts, since my > > porcelain is aimed at my co-workers who are stuck on windows) > > Are you building a strictly Win32 native GUI? Or something else? It's mono/.net, so I can test it on my linux box and push the binary directly to the poor souls on windows :) > Can I ask what sort of features you are going after? (And if > there's a git repository available, feel free to just point me at > it and ignore my questions.) The features I'm focusing on are mostly trivial day-to-day operations of your average coder: status, diff, commit, push, fetch, merge, checkout, log. This should be enough to support our (planned) workflow of one public repo per developer + a shared integration repo with restricted push access + active use of topic-branches. We currently use subversion, so real branches + real merges are killer arguments for a switch to git. But we also use tortoisesvn, and the "simplicity" of the gui must be met by some tool. Hence me playing around.... If/when it becomes useful, I'll put it up on http://hjemli.net/git/ > I'm just curious. We seem to have a lot of user interface projects > going on at once right now (Eclipse plugin, git-gui, gitk, qgit, tig, > gitweb, blameview) and everyone's been learning from each other. Heh, I actually considered calling it yagg (but it doesn't deserve a name yet) > I think the competition is good, there's no clear right way to do > things here. As the primary author of git-gui, I do want to try > and keep current with what the others are up to. ;-) Absolutely, nice work btw. -- larsh