Finally, I found a solution to satisfy my needs. I started a repository
with multiple independent branches. I do checkout the branches as
subdirectories below the trunk checkout with nested checkout. It is a bit
more effort to set things up, but simple scripts can help for that.
Adding branches go
Here’s the use case:
We’re moving from our existing large repo to several smaller ones, in order to
clean up and make our builds more flexible.
One of new repos will start from the current state of old trunk. There are a
couple of active development branches in old repo that will continue
Hi,
I'm trying to move some old project code into a fossil-repository for
better archiving mainly. Currently the repo is under bazaar, where it was
started in.
I tried the way over git format, exporting the bazaar trunk via fast-export
in plain git format and importing that into fossil.
If you l
Is there a way for users to clone all repos in local group supplying user/pwd,
so they can commit?
The 'master' repo can be cloned, but not the 'slaves' (i.e. repos that join the
group, pointing to the master).
If no way, this is a major drawback for multi-repo setup vs single big one.
S.
__
On Fri, Sep 18, 2015 at 1:52 PM, Steve Stefanovich wrote:
> Is there a way for users to clone all repos in local group supplying
> user/pwd, so they can commit?
>
No. There is an 'all' command which can apply some commands (like 'pull')
to all repos fossil knows about, but cloning isn't include
It hasn't got anything to do with sub-repos. If you use login group, you
cannot clone with authorisation any of the repos that joined the group,
sub-repos or not.
This is not optimal because it forces you to duplicate user management in every
repo, or use single big repo instead.
From: Stepha
On Fri, Sep 18, 2015 at 3:05 PM, Steve Stefanovich wrote:
> It hasn't got anything to do with sub-repos. If you use login group, you
> cannot clone with authorisation any of the repos that joined the group,
> sub-repos or not.
>
Ah, a _login group_. i thought, based on recent posts, you meant a
On Fri, Sep 18, 2015 at 9:05 AM, Steve Stefanovich wrote:
> It hasn't got anything to do with sub-repos. If you use login group, you
> cannot clone with authorisation any of the repos that joined the group,
> sub-repos or not.
>
> This is not optimal because it forces you to duplicate user manag
Thus said Steve Stefanovich on Fri, 18 Sep 2015 13:05:57 -:
> If you use login group, you cannot clone with authorisation any of the
> repos that joined the group, sub-repos or not.
I setup a pair of repositories, then ran fossil ui on one of them and
grouped it to the other. Then I added
9 matches
Mail list logo
