* Is there a way to mark a branch as published? @ 2014-07-29 22:40 Nico Williams 2014-08-01 18:58 ` Dennis Kaarsemaker 0 siblings, 1 reply; 3+ messages in thread From: Nico Williams @ 2014-07-29 22:40 UTC (permalink / raw) To: git discussion list (or all of a repo's branches) Teamware recorded whether it had any "children" and warned about rebasing published contents. Perhaps git could do the same. Nico -- ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Is there a way to mark a branch as published? 2014-07-29 22:40 Is there a way to mark a branch as published? Nico Williams @ 2014-08-01 18:58 ` Dennis Kaarsemaker 2014-08-01 19:17 ` Nico Williams 0 siblings, 1 reply; 3+ messages in thread From: Dennis Kaarsemaker @ 2014-08-01 18:58 UTC (permalink / raw) To: Nico Williams; +Cc: git discussion list On di, 2014-07-29 at 17:40 -0500, Nico Williams wrote: > (or all of a repo's branches) > > Teamware recorded whether it had any "children" and warned about > rebasing published contents. Perhaps git could do the same. Git doesn't record this directly, but you can see which known remote branches contain the tip of a branch: git branch -a --contains yourbranchnamehere | grep remotes/ That doesn't say anything about remotes you don't know about of course. -- Dennis Kaarsemaker www.kaarsemaker.net ^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Is there a way to mark a branch as published? 2014-08-01 18:58 ` Dennis Kaarsemaker @ 2014-08-01 19:17 ` Nico Williams 0 siblings, 0 replies; 3+ messages in thread From: Nico Williams @ 2014-08-01 19:17 UTC (permalink / raw) To: Dennis Kaarsemaker; +Cc: git discussion list On Friday, August 1, 2014, Dennis Kaarsemaker <dennis@kaarsemaker.net> wrote: > > On di, 2014-07-29 at 17:40 -0500, Nico Williams wrote: > > (or all of a repo's branches) > > > > Teamware recorded whether it had any "children" and warned about > > rebasing published contents. Perhaps git could do the same. > > Git doesn't record this directly, but you can see which known remote > branches contain the tip of a branch: Yes, but that says nothing about whether they accept non-ff merge pushes, or should reject them, and it says nothing about whether they are intended to be seen as "published" in the sense of having stable history. (Teamware would mark repos as published when cloned, but that often meant needing to reset that flag [it wasn't a flag, but i'm eliding irrelevant details].) Yes, non-fast-forward pushes can be rejected with a hook, but a flag that could be set with a git command would be more convenient. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2014-08-01 19:17 UTC | newest] Thread overview: 3+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2014-07-29 22:40 Is there a way to mark a branch as published? Nico Williams 2014-08-01 18:58 ` Dennis Kaarsemaker 2014-08-01 19:17 ` Nico Williams
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox