In reading today's Dilbert, I imagined how it applies to git:
http://dilbert.com/strip/2018-05-02?utm_source=dilbert.com/newsletter&utm_medium=email&utm_campaign=brand-loyalty&utm_content=strip-image
--
Scott Robison
___
fossil-u
I've done similar work for my own lighttpd based personal server. If you'd
like I can share my config, maybe it would be helpful.
On Feb 26, 2018 1:36 PM, "Roy Keene" wrote:
> Scott,
>
> Fossil can be run in any URL suffix on an existing domain. This
> is how, for example ChiselApp.com
Forged should be a skull and crossbones. I would think yellow and red
unlocked locks and green locked locks, but definitely with hover text for
those of us with faulty color perception.
On Dec 21, 2017 3:16 PM, "Richard Hipp" wrote:
> On 12/21/17, jungle Boogie wrote:
> >
> > How are the signat
I'd bet that you can commit as anyone and push it if you have that access.
You probably wouldn't keep that access for long, though.
On Dec 14, 2017 12:13 PM, "Warren Young" wrote:
> On Dec 14, 2017, at 10:19 AM, jungle Boogie
> wrote:
> >
> > So Warren edited a file at the same exact time as ta
I read that as no, he isn't having the same problem.
On Dec 6, 2017 2:59 PM, "Richard Hipp" wrote:
> On 12/6/17, Stephan Beal wrote:
> > On Wed, Dec 6, 2017 at 8:33 PM, Richard Hipp wrote:
> >
> >> know.) Are you still having the same problem with the latest
> >> code, even after hitting
On phone, apologies in advance for top posting...
The value I see from multi vcs support isn't providing easy setup of
hosting one repo on multiple formats (though that would be awesome). I like
the idea of using fossil at work where I'm forced to use git (or Perforce,
though that hasn't been ment
On Sep 29, 2017 7:43 AM, "Andy Goth" wrote:
On 09/28/17 21:34, Scott Robison wrote:
> There is a winsymlink branch I created some time ago. Hasn't been kept
> up to date (I didn't need it, just thought it might be useful for
> feature parity) but I could take a look
There is a winsymlink branch I created some time ago. Hasn't been kept up
to date (I didn't need it, just thought it might be useful for feature
parity) but I could take a look at it if you were interested. Or you could.
On Sep 28, 2017 7:08 PM, "Andy Goth" wrote:
> http://fossil-scm.org/index.h
I'm on the road and may not be thinking clearly, but if you're trying
to revert your entire tree to the state 6 or 7 commits ago, might it
be easier to update to the commit you want, rename the first commit in
the now unwanted branch, and continue on from the new root?
--
Sco
On Apr 29, 2017 8:30 PM, "The Tick" wrote:
OK, I think I've figured it out!
You're supposed to do a fossil >open< with a version name being "trunk"
(default) or "branch name". When finished, do a fossil close.
It appears that I can even do this in separate directories at the same time
-- one in
On Wed, Apr 12, 2017 at 4:41 PM, Thomas wrote:
> On 2017-04-12 23:24, Scott Robison wrote:
>>
>> When I am using the download from fossil-scm.org, I am able to use
>> single quotes to 'escape' the asterisk. Double quotes do not work.
>
>
> On Window
On Wed, Apr 12, 2017 at 2:10 PM, Thomas wrote:
> On 2017-04-12 18:01, Scott Robison wrote:
>>
>> On Apr 12, 2017 10:31 AM, "Thomas" > <mailto:tho...@dateiliste.com>> wrote:
>>
>> On 2017-04-09 02:19, Richie Adler wrote:
>>
>>
On Apr 12, 2017 10:31 AM, "Thomas" wrote:
On 2017-04-09 02:19, Richie Adler wrote:
> Thomas decía, en el mensaje "[fossil-users] Issue with crlf-glob *" del
> 8/4/2017 17:46:14:
>
> Does anyone know how to unveil the secret of getting the mentioned
>> asterisk into the crlf-glob setting without
On Tue, Apr 11, 2017 at 4:11 PM, Thomas wrote:
> On 2017-04-11 22:51, Scott Robison wrote:
>>
>> On Tue, Apr 11, 2017 at 3:39 PM, Scott Robison
>> wrote:
>>>
>>> On Tue, Apr 11, 2017 at 3:21 PM, Thomas wrote:
>>>>
>>>> On
On Tue, Apr 11, 2017 at 3:39 PM, Scott Robison wrote:
> On Tue, Apr 11, 2017 at 3:21 PM, Thomas wrote:
>> On 2017-04-11 22:11, Thomas wrote:
>>
>> add
>>--ignoreIgnore unmanaged files matching
>> patterns
On Tue, Apr 11, 2017 at 3:21 PM, Thomas wrote:
> On 2017-04-11 22:11, Thomas wrote:
>>
>> On 2017-04-11 22:01, Scott Robison wrote:
>>>
>>> I was thinking about that earlier (well, a warning, not an error,
>>> which presumes you can't continue).
On Tue, Apr 11, 2017 at 3:11 PM, Thomas wrote:
> On 2017-04-11 22:01, Scott Robison wrote:
>>
>> On Tue, Apr 11, 2017 at 2:31 PM, David Mason wrote:
>>>
>>> I think --ignore should give an error if the --ignore matches a file
>>> already
>>> i
On Tue, Apr 11, 2017 at 3:04 PM, Thomas wrote:
> On 2017-04-11 19:34, Scott Robison wrote:
>>
>> No, I try to explain why what you see isn't a design flaw, and
>> apparently fail. But I'll keep trying!
>
>
> Since I've never heard of any software that
On Tue, Apr 11, 2017 at 2:31 PM, David Mason wrote:
>
> On 11 April 2017 at 14:34, Scott Robison wrote:
>>
>> No, it is an explicit command clearly stating the user's desire for
>> exclusion of these files *that are not already under source control*.
>> The f
On Tue, Apr 11, 2017 at 10:36 AM, Thomas wrote:
> On 2017-04-11 05:22, Scott Robison wrote:
>>
>> Perhaps it should be documented, but I don't think it is a bug. It is
>> the software doing the job it was originally told to do (track versions
>> of a file)
On Apr 10, 2017 5:02 PM, "Thomas" wrote:
On 2017-04-10 22:28, Scott Robison wrote:
> On Mon, Apr 10, 2017 at 2:57 PM, Thomas wrote:
>
>> I reckon I owe you a beer! ;-)
>>
>
> Not at all. I don't drink, anyway. Well, not beer. :)
>
You're prob
seems
to have been put in place to check either the file in the repo or the
file on the disk depending on what is available. I don't have time to
understand it completely, but that seems to be the source of my
confusion as to when / where versioned settings are accessed / read.
--
Scott
On Mon, Apr 10, 2017 at 1:58 PM, Thomas wrote:
> On 2017-04-10 20:34, Scott Robison wrote:
>>
>> On Mon, Apr 10, 2017 at 1:05 PM, Thomas wrote:
>>>
>>> On 2017-04-10 20:00, Scott Robison wrote:
>>
>> Let's say you have a repo named bob. You ha
On Mon, Apr 10, 2017 at 1:05 PM, Thomas wrote:
> On 2017-04-10 20:00, Scott Robison wrote:
>>
>> On Apr 10, 2017 12:48 PM, "Thomas" > <mailto:tho...@dateiliste.com>> wrote:
>> Example of .fossil-settings\ignore-glob:
>> *.obj
>>
On Apr 10, 2017 12:48 PM, "Thomas" wrote:
Hello,
As stated in one of my earlier mails, I also got an issue with files to
ignore.
I have now created a folder .fossil-settings and placed the glob files in
it.
Actually, I got a batch file that reads the file filter settings from
another file and
On Apr 8, 2017 3:29 PM, "Thomas" wrote:
On 2017-04-08 21:59, Richard Hipp wrote:
> On 4/8/17, Thomas wrote:
>
>>
>> C:\fos>fossil settings crlf-glob *.obj
>> C:\fos>
>> C:\fos>fossil settings crlf-glob *
>> Usage: fossil settings ?PROPERTY? ?VALUE? ?-global?
>> C:\fos>fossil settings crlf-glob
straightforward two byte encoding back then. As Bill Gates
(then CEO of MS, MS being one of the earliest members of the Unicode
Consortium) said in 1991:
"Okay, so 640K of RAM isn't enough memory, but 64K code points will
definitely encode more characters than we'll ever possibly nee
On Wed, Mar 29, 2017 at 9:46 AM, jungle Boogie wrote:
> On 28 February 2017 at 08:04, jungle Boogie wrote:
>> Hi All,
>>
>> This is most likely a request only Dr. Hipp can fulfill has he has
>> access to all the databases.
>>
>> Is it possible for this chart to be updated?
>> https://www.fossil-s
On Mar 27, 2017 6:44 PM, "Byron Sanchez" wrote:
Recently, however, fossil has started interpreting one of these org-mode
files as a binary file. Now, fossil prompts with it's binary-file warning
each time I update the file. In addition, this file can no longer be diffed
in the web interface, sinc
On Mar 26, 2017 11:25 AM, "Christophe Gouiran"
wrote:
Please find as attached file another patch which:
1. First test for a real terminal before spawning the pager command.
2. No more paginate json command.
I see that most of you complain about this proposed feature.
It was only a propos
On Mar 26, 2017 7:13 AM, "Christophe Gouiran"
wrote:
Hi all,
First of all many thanks for all your feedback.
I come back to you with an implemented solution.
After many thinking, for me not all commands need to send their outputs to
a pager.
Only ones which may output a big amount of lines in
I don't know about what commands to paginate by default, but no to
versionable settings for this. Don't want to force this on others.
On Mar 23, 2017 4:08 PM, "Christophe Gouiran"
wrote:
> Good morning,
>
> I would like to implement the feature given in the title.
> I'm inspired by what Git (by
On Mar 21, 2017 11:04 PM, "Martin Vahi" wrote:
I haven't encountered any collisions yet, but
I was wondering, what will happen, if 2 different
files that have the same size, same timestamps,
different bitstreams, but the same hash (regardless of hash algorithm)
were to be committed simultaneous
On Sat, Mar 11, 2017 at 8:08 AM, Mark Janssen wrote:
> Good questions. Currently it replaces the existing markdown parser which
> can break existing files. This is why I suggested the repo wide setting.
>
Sorry, I missed that part.
> There are other possible solutions (switch on extension being
? If
replace, would it "break" existing repos that are using markdown? If people
have .md files with the existing markdown support, might this need a
different extension?
--
Scott Robison
___
fossil-users mailing list
fossil-users@lis
On Dec 20, 2016 10:59 PM, "John Found" wrote:
Well, the compression is the last thing I am talking about. It is
important, but not essential.
I am talking about several people working on one file and then fossil
merging the
changes automatically (of course if there is no conflicts in the edits).
On Nov 11, 2016 5:28 PM, "K. Fossil user"
wrote:
>
> Ah you don't understand again what I've said ...
>
> 1/ Fossil and SQLite work together, and to be clear, the same guy work
for both projects.
> I was even told that the AIM of Fossil is to help SQLite.
> Do you agree at least with these ?
Yes,
> If you color lines by meaing, it is easier to understand:
Unless you're color blind, in which case it might be impossible to
understand.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/li
at someone will compromise a server with a weak password and
completely replace the good repo with a bad repo, or just host a fork that
looks legit and get people to pull from that instead.
--
Scott Robison
___
fossil-users mailing list
fossil-users
On Oct 16, 2016 6:35 PM, "K. Fossil user"
wrote:
>
> I am angry because Fossil knows nothing about marketing which is bad for
any project...
If I may paraphrase, Fossil's benevolent dictator has stated many times in
the past that the One True Purpose (TM) of Fossil is to serve SQLite
development.
rward slash.
>
> ...and NUL, I beleive.
>
Not to be confused with the DOS/Windows NUL device. :)
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
appear to be ordinary file names. If we do support it, Fossil
potentially looks bad for creating files or directories that other
processes can't interact with normally.
I wouldn't mind taking a stab at it if enough people think it is
worthwhile, but I'm not sure it is worth
On Sun, Sep 11, 2016 at 3:27 PM, Adam Jensen wrote:
> On 09/11/2016 04:42 PM, Scott Robison wrote:
> > I may not be understanding you, but from my point of view, it already
> > does what you want by supporting versioned files that you simply never
> > change. For example,
o estimate where Fossil might
> be a reasonable solution and where some other approach is needed.
>
I may not be understanding you, but from my point of view, it already does
what you want by supporting versioned files that you simply never change.
For example, you could have a repo that has a str
l expects me to read the output to understand the
current state and status of commands issued? That's pretty user
unfriendly...
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On Aug 2, 2016 9:12 AM, "Richard Hipp" wrote:
>
> On 8/2/16, Ron W wrote:
> >
> > Are there really still compilers in use
> > that don't implement C99?
> >
>
> I still build Fossil on a circa-2002 iBook. (See section 4 of
> http://fossil-scm.org/fossil/doc/trunk/www/build.wiki). I do not know
>
What version of fossil are you using? Some changes have been made fairly
recently that you may not have.
On Jul 19, 2016 1:16 AM, "Svyatoslav Mishyn" wrote:
> Hello,
>
> I'm using Fossil to store GPG encrypted passwords;
>
> and one file Fossil detects as UTF-8:
>
> /home/juef/tmp: f test-looks-
On Fri, Jun 17, 2016 at 6:04 PM, Warren Young wrote:
> On Jun 17, 2016, at 1:59 PM, Scott Robison
> wrote:
> >
> > Would it be a bad thing to just settle on LF only going forward, always
> stripping CR?
>
> The argument over canonicalizing all text input to LF has be
t; doesn’t find any, it should strip them out of the changed comment text
> before storing it in the DB.
>
Would it be a bad thing to just settle on LF only going forward, always
stripping CR?
--
Scott Robison
___
fossil-users mailing list
fossil-
On Fri, Jun 10, 2016 at 7:10 PM, Joe Mistachkin
wrote:
>
> Scott Robison wrote:
> >
> > Okay, thanks for all the help. I've committed some new test cases that
> > demonstrate errors in the trunk invalid_utf8. 16 tests fail on trunk,
> > none fail on invalid
On Fri, Jun 10, 2016 at 5:24 PM, Joe Mistachkin
wrote:
>
> Scott Robison wrote:
> >
> > So my expectation that it would automatically update the utf.test file is
> > incorrect? I'm supposed to manually integrate that file back to utf.test?
> >
>
> Yes
On Fri, Jun 10, 2016 at 4:23 PM, Joe Mistachkin
wrote:
>
> Scott Robison wrote:
> >
> > Also: Simply uncommenting the "createTestResults $tempPath 100" call
> doesn't
> > seem to be doing anything for me. Here is what I'm doing:
> >
>
>
On Fri, Jun 10, 2016 at 3:27 PM, Scott Robison
wrote:
> On Fri, Jun 10, 2016 at 12:26 PM, Scott Robison
> wrote:
>
>> On Jun 10, 2016 6:04 AM, "Jan Nijtmans" wrote:
>> >
>> > 2016-06-10 10:12 GMT+02:00 Scott Robison:
>> > > FYI, my
On Fri, Jun 10, 2016 at 12:26 PM, Scott Robison
wrote:
> On Jun 10, 2016 6:04 AM, "Jan Nijtmans" wrote:
> >
> > 2016-06-10 10:12 GMT+02:00 Scott Robison:
> > > FYI, my test code here (C++ harness) consisted of passing every
> possible
> > > f
On Jun 10, 2016 6:04 AM, "Jan Nijtmans" wrote:
>
> 2016-06-10 10:12 GMT+02:00 Scott Robison:
> > FYI, my test code here (C++ harness) consisted of passing every possible
> > four byte buffer to the old function and my new function. My function
> > identifies t
On Fri, Jun 10, 2016 at 2:04 AM, Scott Robison
wrote:
> On Fri, Jun 10, 2016 at 1:37 AM, Joe Mistachkin
> wrote:
>
>>
>> Scott Robison
>> >
>> > Glad to be able to get to something before everyone else for a change.
>> :)
>> >
>>
>&
On Fri, Jun 10, 2016 at 1:37 AM, Joe Mistachkin
wrote:
>
> Scott Robison
> >
> > Glad to be able to get to something before everyone else for a change. :)
> >
>
> Yes, thank you very much.
>
> Also, I know it's not a lot of fun, but...
>
> It woul
On Fri, Jun 10, 2016 at 1:15 AM, Jan Nijtmans
wrote:
> 2016-06-10 2:01 GMT+02:00 Scott Robison:
> > I just committed
> > a one line fix (with multiple lines of comments to clarify what the code
> is
> > doing in the tricky part).
>
> Scott, I owe you. Many thanks!
On Thu, Jun 9, 2016 at 6:19 PM, Warren Young wrote:
> On Jun 9, 2016, at 6:01 PM, Scott Robison wrote:
> >
> > On Thu, Jun 9, 2016 at 2:12 PM, Warren Young wrote:
> > On Jun 9, 2016, at 6:25 AM, rosscann...@fastmail.com wrote:
> > >
> > > The bug:
>
f comments to clarify what
the code is doing in the tricky part).
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
n 7z files! Anything but git!
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On Jun 3, 2016 10:11 AM, "jungle Boogie" wrote:
>
> On 31 May 2016 at 01:58, Scott Robison wrote:
> > Just an announcement in case anyone is using the winsymlink branch
(which
> > seems unlikely to me).
> >
> > I've merged the current trunk into wins
ine when about to add a feature in advance,
rather than wondering why the "crazy user" is asking for already
implemented functionality.
DRH: I suspect you never sleep.
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Just an announcement in case anyone is using the winsymlink branch (which
seems unlikely to me).
I've merged the current trunk into winsymlink. The only functionality
exposed in the winsymlink branch, other than what's in trunk, is Windows
symbolic links.
Carry on.
--
Sco
day in the office because I needed to
coordinate with people more closely than I could remotely.
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On Wed, May 18, 2016 at 1:31 PM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:
> On Wed, 18 May 2016 13:12:30 -0600
> Scott Robison wrote:
>
> [...]
> > Yes, I dislike git (though TortoiseGit makes it a lot more
> > tolerable). I don't blame g
ave number choices of rants to read online. I and the entire
Scott Robison team would like to thank you for choosing us over the
competition.
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
t a (perhaps restricted) squash command which would
> only
> work on private branches?
> :-)
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
--
Scott Robison
___
Note that you have to merge mybranch back to trunk, otherwise all the
changes made in mybranch will live happily over there forever. Once you
updated to trunk, you abandoned all committed work from the other branch.
On Sat, Apr 30, 2016 at 11:27 PM, Scott Robison
wrote:
> I think that'
tyle=*dotted*,color=*red*];
>*merge*->*3*[color=*red*];
>*2*->*3*[weight=*8*];
>
>*trunk*->*developerB*[style=*dotted*,color=*blue*];
>*developerB*->*2*[style=*dotted*,color=*blue*];
> }
>
>
>
>
>
>
> __
cestor VERSION or version from
> another branch?…I hope you’re saying that this is in order to merge another
> branch into this one…within the repo. Yes?
>
> its not clear to me how I can create a merged branch somewhere that has
> all of t
;-)
> > fossil update
> (code review my branch)
>switch context back to trunk for their checkout, not sure exact command
> to use yet)
> fossil merge mybranch
> > (final feature test)
> > fossil commit
>
>
> __
Make that "fossil status or changes or extras or some combination thereof".
On Apr 30, 2016 6:32 PM, "Scott Robison" wrote:
>
> On Apr 30, 2016 6:00 PM, "Steve Schow" wrote:
> >
> > I forgot one step in this process I want:
> >
&
On Apr 30, 2016 6:00 PM, "Steve Schow" wrote:
>
> I forgot one step in this process I want:
>
>
> On Apr 30, 2016, at 5:56 PM, Steve Schow wrote:
>
> >
> >
> > fossil checkout trunk
> > (work on code)
> > fossil commit —branch mybranch
> > (work on more code)
> > fossil commit
> > (code review)
On Apr 25, 2016 8:48 AM, "Michael Richter" wrote:
>
> I know that every time I mention this I get silently, perhaps even
hostilely, ignored, but really guys, why not just use fsl for your
customization needs?
I don't use fsl myself, though I have no quarrel with its existence. I
think inferring h
On Apr 24, 2016 4:07 AM, "Marko Käning" wrote:
>
> Hi devs,
>
> it would be great if one could colorise Fossil’s output on the console!
>
> Quite a few times I missed an error or warning message which slipped in
between of many lines of the usual fossil output on the console.
>
> Red colouring of
ook, Twitter, or
YouTube for my data in a disaster recovery situation. I haven't had to
recovery any data yet, but I'm certain it will be a cinch. ;)
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
n't think the question "which workspace am I in" vs "what is the
current branch" is any more difficult. And it saves the whole "I have to
stash my current state so I can switch branches and do some work then
switch back and unstash and so on".
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On Thu, Apr 7, 2016 at 4:45 AM, Scott Robison
wrote:
> What is the branch tag reported by fossil status? Perhaps the branch you
> were on got renamed?
>
> On Thu, Apr 7, 2016 at 2:43 AM, John Regehr wrote:
>
>> Hi Andy,
>>
>> I'm returning to this topi
the remote changes in the timeline in your local repository and
>> Fossil simply does not update your open checkout to those versions of
>> the file? Or do you not see the changes at all?
>>
>> Can you provide some output from the com
On Fri, Feb 19, 2016 at 4:55 PM, Warren Young wrote:
> On Feb 18, 2016, at 7:20 PM, Scott Robison
> wrote:
> >
> > As it turns out, this wasn't a great plan.
>
> I agree. I even dislike checking configure scripts generated by autoconf
> and similar into repos.
&
will Just Work(TM) on your
repository setup. It makes assumptions likely unique to my configuration
(hard coded paths, a single user name being used for all commits, no
branches, maybe more). Still, it might be a useful reference.
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On Sun, Feb 14, 2016 at 9:57 PM, Warren Young wrote:
> On Feb 13, 2016, at 10:41 PM, Scott Robison
> wrote:
> >
> > I wonder if I could build fossil for my old Commodore 64.
>
> No way. Contemporary compilers would have been pre-ANSI, so they wouldn’t
> even underst
On Sun, Feb 14, 2016 at 5:33 PM, Andy Bradford
wrote:
> Thus said Scott Robison on Sun, 14 Feb 2016 05:10:49 -0700:
>
> > There is a lot of intelligence that goes into mailing lists that might
> > not be captured in the repository without extra effort.
>
> I don't
On Sun, Feb 14, 2016 at 4:22 AM, j. van den hoff
wrote:
>
> On Sun, 14 Feb 2016 02:12:01 +0100, Boruch Baum
wrote:
>
>> After Warren Young commented on the "flatness" of forum-style
>> discussions instead of the "threaded" viewing option in email-list-style
>> discussions, I realized that Wikiped
r.
>
> Andy
> --
> TAI64 timestamp: 400056c003e8
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
--
Scott Robison
__
my own PHP based front end to a multi-repo fossil setup that
allows me to create a repo using any of the others as a "template" and
specify the project name & description. It uses SQL to tweak the settings
rather than anything specific to fos
On Thu, Dec 17, 2015 at 3:33 PM, Warren Young wrote:
> On Dec 16, 2015, at 5:25 PM, Scott Robison
> wrote:
> >
> > fossil commit -m "" --branch sue --private
>
> It never occurred to me that you could combine --branch and --private,
> probably because th
also learned that no Microsoft
> product
> (including MSSQL Server, Excel and Access) can import the
> standards-compliant
> file linked in the article. So apparently your use of JSON was the safest
> course of action.
>
Microsoft software has been exporting and importing C
can merge that branch to trunk.
I'm not trying to suggest it is in any way nearly as "elegant" as "rebase
-i" (those who prefer that would find this clunky at best). Still, it seems
possible.
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On Wed, Dec 16, 2015 at 6:41 PM, Ron W wrote:
> On Wed, Dec 16, 2015 at 6:53 PM, Scott Robison
> wrote:
>
>> > You can remove all private branches from a repository using this
>> command:
>> > fossil scrub --private
>> > Note that the above is a perm
d, Dec 16, 2015 at 5:23 PM, Scott Robison
wrote:
> That is exactly what I mean. I'll see what I can do later to provide a
> transcript.
>
> On Wed, Dec 16, 2015 at 5:18 PM, Warren Young wrote:
>
>> On Dec 16, 2015, at 4:58 PM, Scott Robison
>> wrote:
>> &
That is exactly what I mean. I'll see what I can do later to provide a
transcript.
On Wed, Dec 16, 2015 at 5:18 PM, Warren Young wrote:
> On Dec 16, 2015, at 4:58 PM, Scott Robison
> wrote:
> >
> > On Wed, Dec 16, 2015 at 4:53 PM, Warren Young wrote:
> >
>
On Wed, Dec 16, 2015 at 4:53 PM, Warren Young wrote:
> On Dec 16, 2015, at 2:28 PM, Scott Robison
> wrote:
> >
> > couldn't 99% of rebase use cases be handled with private branches?
>
> Probably not with the current design. For one thing, there are no
> “branche
On Wed, Dec 16, 2015 at 4:12 PM, wrote:
>
> Hmm.. If one can create a private branch, do all draft work there and
when done merge to trunk (or other non-private branch), then sync with the
main repo, the main repo will not contain any traces of the private branch
(with the draft work). Am I corre
the tip of my private branch 100% pristine
and proper, and only then merge it to trunk. I could just as easily have
created a new branch off the tip of trunk,and merged my private branch to
the public branch, which I could then merge to trunk so that people aren't
upset at me for working on
Is a sql database fault tolerant? I guess so, but think that is not what
most people consider fault tolerant.
On Dec 16, 2015 9:36 AM, "Stephan Beal" wrote:
> Section 4.1: in fossil, but not git: fault-tolerant storage.
>
> - stephan beal, sgb...@googlemail.com
> Written on a keyboard attache
e by rebasing your branch.
4a. Merge your branch to trunk and only push trunk.
4b. Push your branch and merge it.
5. Delete branch.
This workflow makes me long for the days where all I had to worry about was
a usually simple rebase operation.
--
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
On Nov 18, 2015 1:28 AM, "Stephan Beal" wrote:
>
> On Wed, Nov 18, 2015 at 9:19 AM, Dömötör Gulyás
wrote:
>>
>> And unfortunately not all devs sit in the same building. Anyway, I'll
just upload a repo, probably most people will just read it, and when
changes are to be made, it'll be on me to mana
le?
>
> Cheers & thanks,
> DG
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
--
Scott Robison
___
fossil-users mailing list
fos
1 - 100 of 259 matches
Mail list logo
