{"thread":{"id":"37244","subject":"Is there a way to mark a branch as published?","startedAt":"2014-07-29T22:40:45Z","lastAt":"2014-08-01T19:17:34Z","messageCount":3,"participants":["Nico Williams","Dennis Kaarsemaker"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"246952","messageId":"CAK3OfOjPQ1fcoA7O6EDcQ3iW_AdsjitK4WKSdLwpRRXm8xfrVA@mail.gmail.com","threadId":"37244","inReplyTo":null,"subject":"Is there a way to mark a branch as published?","fromName":"Nico Williams","fromEmail":"nico@cryptonector.com","sentAt":"2014-07-29T22:40:45Z","receivedAt":"2014-07-29T22:40:45Z","isPatch":false,"sender":{"key":"nico@cryptonector.com","avatar":null},"body":"(or all of a repo's branches)\n\nTeamware recorded whether it had any \"children\" and warned about\nrebasing published contents.  Perhaps git could do the same.\n\nNico\n--\n"},{"id":"247122","messageId":"1406919490.3253.3.camel@spirit","threadId":"37244","inReplyTo":"CAK3OfOjPQ1fcoA7O6EDcQ3iW_AdsjitK4WKSdLwpRRXm8xfrVA@mail.gmail.com","subject":"Re: Is there a way to mark a branch as published?","fromName":"Dennis Kaarsemaker","fromEmail":"dennis@kaarsemaker.net","sentAt":"2014-08-01T18:58:10Z","receivedAt":"2014-08-01T18:58:10Z","isPatch":false,"sender":{"key":"dennis@kaarsemaker.net","avatar":"https://avatars.githubusercontent.com/u/200649?v=4"},"body":"On di, 2014-07-29 at 17:40 -0500, Nico Williams wrote:\n> (or all of a repo's branches)\n> \n> Teamware recorded whether it had any \"children\" and warned about\n> rebasing published contents.  Perhaps git could do the same.\n\nGit doesn't record this directly, but you can see which known remote\nbranches contain the tip of a branch:\n\ngit branch -a --contains yourbranchnamehere | grep remotes/\n\nThat doesn't say anything about remotes you don't know about of course.\n-- \nDennis Kaarsemaker\nwww.kaarsemaker.net\n"},{"id":"247125","messageId":"CAK3OfOgxngLhh7FjrBT9NcK=LhEH9TAz+18LAvXJtt_bV=96wA@mail.gmail.com","threadId":"37244","inReplyTo":"1406919490.3253.3.camel@spirit","subject":"Re: Is there a way to mark a branch as published?","fromName":"Nico Williams","fromEmail":"nico@cryptonector.com","sentAt":"2014-08-01T19:17:34Z","receivedAt":"2014-08-01T19:17:34Z","isPatch":false,"sender":{"key":"nico@cryptonector.com","avatar":null},"body":"On Friday, August 1, 2014, Dennis Kaarsemaker <dennis@kaarsemaker.net> wrote:\n>\n> On di, 2014-07-29 at 17:40 -0500, Nico Williams wrote:\n> > (or all of a repo's branches)\n> >\n> > Teamware recorded whether it had any \"children\" and warned about\n> > rebasing published contents.  Perhaps git could do the same.\n>\n> Git doesn't record this directly, but you can see which known remote\n> branches contain the tip of a branch:\n\nYes, but that says nothing about whether they accept non-ff merge\npushes, or should reject them, and it says nothing about whether they\nare intended to be seen as \"published\" in the sense of having stable\nhistory.  (Teamware would mark repos as published when cloned, but\nthat often meant needing to reset that flag [it wasn't a flag, but i'm\neliding irrelevant details].)\n\nYes, non-fast-forward pushes can be rejected with a hook, but a flag\nthat could be set with a git command would be more convenient.\n"}]}