On Fri, May 25, 2012 at 1:51 PM, Lluís Batlle i Rossell <vi...@viric.name>wrote:

> On Fri, May 25, 2012 at 01:49:06PM -0400, Richard Hipp wrote:
> > On Fri, May 25, 2012 at 1:42 PM, Lluís Batlle i Rossell <
> vi...@viric.name>wrote:
> >
> > > >
> > > > 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?
> > >
> >
> >
> > There is no easy way to make a branch public.  It *might* work to go
> > through an cancel the "private" tag on each check-in of the branch, then
> > run "rebuild".  Emphasis is on the word "might" because I have never
> > actually tried to do that.  And, there is no way that I know of to cancel
> > the tag on all checkins of a branch all at once - you'd have to do them
> one
> > by one.
>
> Ah, I thought that branches could be made back public easily. I never used
> privated branches still, so I have zero practise with them.
>
> As for the tag, Why it does not work as in an inherited tag?
>

The "private" tag is hard-coded onto every check-in of a private branch.
You can override the tag later.  But there is still a new instance of the
tag on every check-in and each new instance has to be cancelled separately.


>
> Thank you,
> Lluís.
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>



-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
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