On Mon, Dec 26, 2016 at 7:00 AM, <[email protected]> wrote: > > Date: Sun, 25 Dec 2016 18:07:18 +0000 > From: Chad Perrin <[email protected]> > Subject: Re: [fossil-users] incorrect user info in export --git > > On Sun, Dec 25, 2016 at 12:22:43PM -0500, Ron W wrote: > > > > Then I commit the "final" > > changes to my clone and send the pull request. > > That sounds like a use case for what I've built, >
Not really. I don't need/want to make more than the one commit to git, so not exporting anything to git. And really no need to import from git, either. At most, I treat the coded from the git repo as a "vendor branch" holding only the few git commits relevant to the change I'm making. The rest of the git history doesn't need to be in Fossil. > > > > > At work, the controls software group uses Fossil "internally", but the > > company is still "standardized" on SVN (because the IT group's vision is > > for "thin client" PCs that are fully interchangeable, which doesn't work > > for my group because we need specialized tool chains that don't "play > well" > > with IT's vision). We use Fossil for our day-to-day work, only committing > > releases to SVN. > > It seems like you have need of tools for import/export mirroring with > Subversion, too. > Don't need nor want the day-to-day history in SVN. Only making commits of the released versions to SVN because the company requires it. Otherwise, we treat the the SVN repo as "write only". The SVN commit is automated as part of the process for creating the release "package".
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
