On 11/2/20 5:30 PM, Josh Sled wrote: > Anthony Carrico <[email protected]> writes: > Same. On my homebrew NAS¹, `earth`, I have a git user running the git-shell:
Another approach to multiple users is to set the 'core.sharedRepository' option. Using 'git init --bare --shared', will set it to 'group'. > I mean, I know why it hasn't, and keeping the issues in a separate > branch loses a lot of the value, especially if you use any reasonable > branched development model, but then keeping up with a maybe-voluminous > stream of "unrelated" issue-maintenance commits is a chore, especially > if you believe in the supremacy of rebase vs. merge workflows, and and > and … :) I think one of the issues is that with git (vs. svn or perforce) you can't really have two branches out at a time. I think this makes using branches a little problematic for this kind of workflow and others. Sometimes I'd like to branch two projects (histories) from the initial commit, but in git you can never see them at the same time. -- Anthony Carrico
