On 12/6/06, Brian Paul <[EMAIL PROTECTED]> wrote: > Brian Paul wrote: ... > Kristian reminded me: > """ > Just a heads up to those that have used the git mirror I had running > prior to this: the new official repo is a new import from scratch, > since I used a more complete authors list and thus the sha1 sums are > all different. > > If you have changes in a repo clone from my mirror, you can extract > them using e.g. git-format-patches and re-apply in the new repo. > """
Oh, oops, I wanted to send that to the list too, thanks for forwarding it. And it looks like there's an origin branch in the repo now. This happens when you just say git push to push changes instead of git push origin well... AFAIK, anyway. The 'origin' branch is a branch that gets created when you clone a repo and it's always identical to the 'master' branch in the repo you clone from. Pushing the 'origin' branch is a common pitfall, and I believe it's a behaviour that has been fixed in recent git version. It's pretty harmless, but somebody with access to the upstream repo (which why I'm cc'ing Keith and Daniel) need to remove the branch there. Another common mistake with the git commit message format. There is a convention that the first line in the commit message should be a single short summary, optionally followed by a blank line and then a more detailed description if you're so inclined: http://git.or.cz/gitwiki/CommitMessageConventions cheers, Kristian ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
