{"thread":{"id":"10062","subject":"git-svn eliminating master","startedAt":"2007-09-28T20:01:51Z","lastAt":"2007-09-28T22:34:17Z","messageCount":3,"participants":["Russ Brown","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"54288","messageId":"46FD5DAF.7030204@gmail.com","threadId":"10062","inReplyTo":null,"subject":"git-svn eliminating master","fromName":"Russ Brown","fromEmail":"pickscrape@gmail.com","sentAt":"2007-09-28T20:01:51Z","receivedAt":"2007-09-28T20:01:51Z","isPatch":false,"sender":{"key":"pickscrape@gmail.com","avatar":null},"body":"So I've been using git-svn for a while, and just decided to try\npublishing my repo via gitweb so I can experiment with showing others my\nlocal branches before I dcommit them to the subversion repository (i.e.\nallowing code review prior to commit).\n\nIt's working pretty nicely: the only problem I have is the master\nbranch. I don't use master at all, and I'm willing to be that a lot of\nother git-svn users don't either. I take all of my branches from either\ntrunk or one of the other upstream svn server branches.\n\nThe problem is gitweb appears to show the master branch by default,\nwhile I'd rather show trunk by default. Is it legal to just delete the\nmaster branch, or failing that have it automatically follow trunk so I\ndon't have to rebase it every time I want to push? Personally I'd rather\ndelete it because it's not used at all in my case and will only lead to\nconfuse the other developers who decide to look at my repo.\n\nI've tried deleting master in a test repo, and it seems to be fine. But\nI don't know if there are any hidden surprised that might come back to\nbite me later.\n\nThanks.\n\n-- \n\nRuss\n"},{"id":"54293","messageId":"7vlkaqo49n.fsf@gitster.siamese.dyndns.org","threadId":"10062","inReplyTo":"46FD5DAF.7030204@gmail.com","subject":"Re: git-svn eliminating master","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2007-09-28T21:43:00Z","receivedAt":"2007-09-28T21:43:00Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Russ Brown <pickscrape@gmail.com> writes:\n\n> So I've been using git-svn for a while, and just decided to try\n> publishing my repo via gitweb so I can experiment with showing others my\n> local branches before I dcommit them to the subversion repository (i.e.\n> allowing code review prior to commit).\n>\n> It's working pretty nicely: the only problem I have is the master\n> branch. I don't use master at all, and I'm willing to be that a lot of\n> other git-svn users don't either. I take all of my branches from either\n> trunk or one of the other upstream svn server branches.\n>\n> The problem is gitweb appears to show the master branch by default,\n> while I'd rather show trunk by default.\n\nI think gitweb shows wherever HEAD points at.  Update the file\non the server and see if it helps.\n"},{"id":"54298","messageId":"46FD8169.6040505@gmail.com","threadId":"10062","inReplyTo":"7vlkaqo49n.fsf@gitster.siamese.dyndns.org","subject":"Re: git-svn eliminating master","fromName":"Russ Brown","fromEmail":"pickscrape@gmail.com","sentAt":"2007-09-28T22:34:17Z","receivedAt":"2007-09-28T22:34:17Z","isPatch":false,"sender":{"key":"pickscrape@gmail.com","avatar":null},"body":"Junio C Hamano wrote:\n> Russ Brown <pickscrape@gmail.com> writes:\n> \n>> So I've been using git-svn for a while, and just decided to try\n>> publishing my repo via gitweb so I can experiment with showing others my\n>> local branches before I dcommit them to the subversion repository (i.e.\n>> allowing code review prior to commit).\n>>\n>> It's working pretty nicely: the only problem I have is the master\n>> branch. I don't use master at all, and I'm willing to be that a lot of\n>> other git-svn users don't either. I take all of my branches from either\n>> trunk or one of the other upstream svn server branches.\n>>\n>> The problem is gitweb appears to show the master branch by default,\n>> while I'd rather show trunk by default.\n> \n> I think gitweb shows wherever HEAD points at.  Update the file\n> on the server and see if it helps.\n\nNice tip. I've updated that now. I'll know if it's worked once trunk\ngets committed to again: I've rebased master against it so both\ncurrently point at the same commit.\n\n-- \n\nRuss\n"}]}