On Fri, May 25, 2012 at 01:34:54PM -0400, Richard Hipp wrote: > On Fri, May 25, 2012 at 1:09 PM, <org.fossil-scm.fossil-us...@io7m.com>wrote: > > > On Fri, 25 May 2012 16:10:44 +0000 > > <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. > > > > Is it possible to get those commits into trunk in any way? Losing the > > details isn't acceptable (due to my misunderstanding of exactly what > > a private branch entailed). > > > > I don't think so, not other than checking each one out and recommitting > them one by one. To do otherwise would be changing the history of the > project, which Fossil does not allow (by design).
Couldn't the branch be made public just before merging? _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
