GUI and detatched HEAD (was Re: Deleting remote branch pointed by remote HEAD)
- From
Daniel Barkalow <barkalow@iabervon.org>
- Date
- Jan 21, 2009, 22:56 UTC
- Message-ID
- <alpine.LNX.1.00.0901211705280.19665@iabervon.org>
- In-Reply-To
- <slrngnedkm.apk.sitaramc@sitaramc.homelinux.net>
On Wed, 21 Jan 2009, Sitaram Chamarty wrote:
Show 17 quoted lines
> On 2009-01-21, Marc-André Lureau <marcandre.lureau@gmail.com> wrote: > > > I deleted a remote branch which was pointed by HEAD, this way: "git > > push origin :master" > > > > Then for almost every git command, I get this error: "error: > > refs/remotes/origin/HEAD points nowhere!". > > > > I found this situation non-friendly. Fortunately, I could understand > > what's going on. But a new user might be confused. > > That's a pretty advanced command for a beginner. I have > people who're only using the GUI (in the presumption that it > will be less confusing or less powerful or whatever) and > have managed to right click on a remote branch, choose > "checkout this branch" and have made commits on it without > knowing they're not on any branch!
I wonder if the GUI could handle this in a way that users would understand. This is qualitively like following a link to a spreadsheet in your web browser, having the browser launch your office suite and load the spreadsheet off the web; now you're interacting with a spreadsheet where you obviously can't save to the original location (which is some web site) and haven't provided a local filename to save as.
I think the right thing would be to show it as "(Untitled)" and have a prominant button to make a real saved branch out of it. There's nothing all that strange about having a current "document" that has no filename yet; the strange thing is that a version control system has this capability.
-Daniel *This .sig left intentionally blank*