On Fri, 25 May 2012 10:18:34 -0700
Matt Welland <estifo...@gmail.com> wrote:

> On Fri, May 25, 2012 at 9:10 AM,
> <org.fossil-scm.fossil-us...@io7m.com>wrote:
> 
> > On Fri, 25 May 2012 11:53:35 -0400
> > Richard Hipp <d...@sqlite.org> wrote:
> >
> > > On Fri, May 25, 2012 at 11:42 AM,
> > > <org.fossil-scm.fossil-us...@io7m.com>wrote:
> > > > Is it possible to avoid squashing all private commits into one?
> > > >
> > >
> > > The branch is private.  If all the individual commits where pushed
> > > out to the world, it wouldn't be private any more and the whole
> > > purpose of having a private branch would be defeated, no?
> > >
> >
> > That's one interpretation of private, yes. I took it to mean that
> > the branch wouldn't be synced, or visible, on any remotes. I don't
> > think that necessarily implies coalescing commits like that...
> >
> > If it's not possible, I can live with it, I'll just switch to only
> > using public branches.
> 
> 
> It sounds like the request would be able to switch a branch from
> private to public. That seems like it would be a very powerful
> feature (assuming it is not already possible?).

Yeah, I think the direct approach would be (if the feature existed):

1. Undo the "merge" commit (perhaps by shunning).
2. Mark the private branch as public.
3. Merge again.


_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to