Re: [fossil-users] Multiple Projects in one Repo

On Sat, Sep 12, 2015 at 8:34 AM, Oliver Friedrich < redtalonof+mailingl...@gmail.com> wrote: > > My current solution is to have one repository with an empty initial > check-in tagged as ROOT. Then I do one branch per sub-project based on the > ROOT check-in. > > That way I'm able to keep my code

Re: [fossil-users] Multiple Projects in one Repo

On 9/12/15, Oliver Friedrich wrote: > I have bunch of code-samples and abstracted code-problems in > different programming languages and flavours, that I keep as personal > knowledge database. I tend to give each of them its own fossil repository, > but as I

Re: [fossil-users] diff after update

On 13 September 2015 at 02:21, Andy Bradford wrote: > Thus said Warren Young on Fri, 11 Sep 2015 18:27:36 -0600: > > > Also, it implies that you're asking Fossil to undo changes, modified > > in some way using diffs. > > Fair enough. I only expressed my opinion about

Re: [fossil-users] diff after update

Thus said Warren Young on Fri, 11 Sep 2015 18:27:36 -0600: > Also, it implies that you're asking Fossil to undo changes, modified > in some way using diffs. Fair enough. I only expressed my opinion about where I thought it fit, with the intention of avoiding having yet another word or

[fossil-users] Cannot set remote-url password when running Fossil non-interactively

Hi, In my application (Fuel) users can set the default remote url for their repositories. The application spawns Fossil with the "remote-url " parameters. It appears however that when urls contain passwords, Fossil does not store the provided password. I think that the problem lies with the way

Re: [fossil-users] diff after update

On Sep 11, 2015, at 7:19 PM, Scott Robison wrote: > On Fri, Sep 11, 2015 at 6:07 PM, Steve Stefanovich wrote: > Clever, but awkward in my opinion; the first place to look for such a feature > would be under diff command. At least for me, that is. > > My

Re: [fossil-users] diff after update

If I understand things right, this is a diff against the undo buffer, so I suggest this alternative: fossil diff --undo-buffer BR, Johan El 13/9/2015 5:39, "Lonnie Abelbeck" escribió: > > On Sep 11, 2015, at 7:19 PM, Scott Robison > wrote: >

Re: [fossil-users] Why Hash

On Sat, Sep 12, 2015 at 12:57 AM, Warren Young wrote: > For instance, why even mention “SHA1 Hash” on the checkin details page in > fossil ui, from src/info.c? Why not something more generic, like “checkin > ID”? > The checkin ID is the hash of the manifest for the checkin.

Re: [fossil-users] diff after update

On Sat, Sep 12, 2015 at 2:04 AM, Scott Robison wrote: > On Fri, Sep 11, 2015 at 5:14 PM, Andy Bradford > wrote: > >> Thus said Richard Hipp on Fri, 11 Sep 2015 10:11:30 -0400: >> >> > "fossil diff --versus-undo" maybe??? >> > i don't like

Re: [fossil-users] diff after update

On Sat, 12 Sep 2015 01:45:28 +0200, Johan Kuuse wrote: fossil diff -before or fossil diff -before-commit typo... I just wanted to propose another name for the requested option, and actually I meant "call it `diff --before' or `diff --before-update' which I for one would

[fossil-users] FOSSIL LS bug?

With this setting: relative-paths (local) 1 doing FOSSIL LS . from within a subdirectory displays the full path (from the root or the repo). I tried with older version and current trunk and get the same behavior. ___ fossil-users mailing list

Re: [fossil-users] diff after update

On Sat, Sep 12, 2015 at 1:10 PM, j. van den hoff wrote: > personally, I find reference to the undo buffer a long way from being > obvious to someone just using fossil as DVCS (rather than someone > interested in in the details/internals of `fossil'). while i can

Re: [fossil-users] Multiple Projects in one Repo

If I get your script right, then I would have one fossil repository for each sub-project and one for the top-project. So with nested repositories my administration overhead would exceed even the single repository solution, right? Johan Kuuse schrieb am Sa., 12. Sep. 2015 um 16:27

Re: [fossil-users] diff after update

On Sat, Sep 12, 2015 at 01:10:28PM +0200, j. van den hoff wrote: > On Sat, 12 Sep 2015 01:45:28 +0200, Johan Kuuse wrote: > > >fossil diff -before > > > >or > > > >fossil diff -before-commit > > typo... I just wanted to propose another name for the requested > option, and actually

Re: [fossil-users] Multiple Projects in one Repo

Hi, After some suggestions in this ML, I chose using nested repositories. The "root repository", which I called 'nested', only contains a few files. All other repositories are open inside the 'nested' directory, with the -nested option. Here is a script which clones, opens and updates the entire

[fossil-users] Multiple Projects in one Repo

I want to give a thought on how I use fossil regularly and on what I would love as a feature. While fossil is easy to set up and maintain, I often have several small projects that seem to be to small to get an own instance of a repository for themselfes. Additionally, I like to use fossil,

Re: [fossil-users] Multiple Projects in one Repo

Hello, On 12 September 2015 at 14:34, Oliver Friedrich wrote: > I want to give a thought on how I use fossil regularly and on what I would > love as a feature. > > While fossil is easy to set up and maintain, I often have several small > projects that seem to be

Re: [fossil-users] Why Hash

On Fri, Sep 11, 2015 at 04:57:46PM -0600, Warren Young wrote: > I wonder if this is an implementation detail leaking through into the > UI, though. Under what conditions, except for Noam’s contrived example > with hardcoded dates, is there a useful distinction between “hash” — > implying a number