I'm thinking I might want the ability to describe branches and tags
separate from the check-in comments.
Maybe a wiki page with the same name as the branch or tag would serve
the purpose, then in the wiki page there could be links to tickets or
whatever else is needed to describe what is going
Subversion revision tagging works fine but has the drawback of
cluttering the tag list. The Subversion repository I'm working with has
over 10K revisions, so that means 10K tags dumped in the tag list, which
I would have preferred to keep clear for activity and release labels and
the like.
Is the Subversion import code supposed to work with incremental delta
input? I find it crashes right away.
My understanding is it looks in the temporary xfiles table to get the
uuid (therefore rid) of existing files (on a given branch), then gets
the blob against which the delta is to be
I think perhaps you meant “commit” comment below? Its the commit comment that
needs to be tweaked, in theory, by the TH1…not the ticket itself. So are you
saying that modifying a commit comment requires that an artifact be created
with TH1 somehow, if even possible?
For the ticket table, I
On Fri, May 20, 2016 at 2:21 AM, Steve Schow wrote:
> Hmm, very interesting idea about using the EDITOR feature to run a
> pre-script…i will have to ponder that…possibly an alternative to using an
> actual wrapper script….
>
> Sounds like server side TH1 probably won’t do it.
>
Hmm, very interesting idea about using the EDITOR feature to run a pre-script…i
will have to ponder that…possibly an alternative to using an actual wrapper
script….
Sounds like server side TH1 probably won’t do it.
throwing a table into the checkout DB would be easy enough to do…can use sqlite
yes I already understood that, I just couldn’t figure out why my fossil mv
command wasn’t working
On May 19, 2016, at 3:55 PM, Warren Young wrote:
> On May 19, 2016, at 11:51 AM, Steve Schow wrote:
>>
>> right, so how do i move a file in the repo from its
7 matches
Mail list logo