On Fri, Mar 9, 2012 at 13:02, Thomas Stover wrote:
> -Algorithmically verify that changes are signed by trusted users on push/pull
> operations.
> (this is also a question)
>
Theoretically, it is sufficient to sign a leaf manifest so that entire
part of the DAG that grows out of this leaf by fol
I'm trying to follow along here, and have a few abstract questions.
If an attacker takes control over a repository, then that repository is
compromised, and would need to be restored from a non-compromised back up. By
compromised we mean someone deleted it, defaced it, or worse tries to hide
ma
I believe I was not clear: I am looking for a side-by-side diff for files in
the 'normal' repository and their check-out counterparts, I am no interested
in the wiki here.
(I just mentioned the wiki as an example where Fossil presents information
from files that are not yet checked in so the tech
On Fri, Mar 9, 2012 at 11:12 AM, Stephan Beal wrote:
> On Fri, Mar 9, 2012 at 5:05 PM, Richard Hipp wrote:
>
>> It is theoretically possible to display a "graph" of changes to the wiki
>> page, similar to the graphs that display on a timeline. And it is possible
>> to have branches on a wiki pa
On Fri, Mar 9, 2012 at 5:05 PM, Richard Hipp wrote:
> It is theoretically possible to display a "graph" of changes to the wiki
> page, similar to the graphs that display on a timeline. And it is possible
> to have branches on a wiki page and to merge, etc. The underlying data
> format supports
On Fri, Mar 9, 2012 at 10:24 AM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:
> On Fri, 9 Mar 2012 11:37:37 +0100
> "Jos Groot Lipman" wrote:
>
> > Is it possible to see a side-by-side difference between the last
> > checkin and the currently changed file on disk? It would be a g
On Fri, Mar 9, 2012 at 4:24 PM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:
> Sorry for nitpicking, but I maintained an impression wiki pages are
> unversioned, only embedded documentation pages are and such preview of
> the "checked out version" is rather implemented for embedde
On Fri, 9 Mar 2012 11:37:37 +0100
"Jos Groot Lipman" wrote:
> Is it possible to see a side-by-side difference between the last
> checkin and the currently changed file on disk? It would be a great
> alternative to fossil diff and fossil gdiff
>
> This would be much like the wiki preview using /d
Lol...
coincidently i was just reading:
http://www.boost.org/doc/libs/1_49_0/libs/filesystem/v3/doc/tutorial.html
and their "tut5.cpp" example demonstrates using \u263A (a smiley face!) in
filenames.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_
On Fri, Mar 9, 2012 at 07:11, Stephan Beal wrote:
>
> Perhaps we could/should make the set of illegal characters a config option,
> defaulting to the current set?
>
This may cause problem with globing.
--Leo--
___
fossil-users mailing list
fossil-users
On Fri, 9 Mar 2012 06:51:14 -0500
Leo Razoumov wrote:
> one size fits all does not work in real life.
I'm aware of it.
> For instance, brackets, spaces, etc. are used in file names generated
> by certain medical imagining machines.
Do those 'medical' machines create text files?
> And when y
On Fri, Mar 9, 2012 at 1:04 PM, Ramon Ribó wrote:
> To create a fossil branch with the modification is a practical idea only
> if you are a lonely developer or in a very controlled team. How do you say
> to a new developer?: Please use fossil, but not the standard one, because
> it has a strang
Leo,
I think that you have described fairly well the situation.
I am a Unix/Windows user since the Silicon Graphics time. I would never
put brackets on a file name. However, I fail to understand why the SCM tool
should prohibit to do so to people that think differently. Specially on
Windows
On Fri, Mar 9, 2012 at 04:18, Gour wrote:
>
> What do you mean 'pre-existing'? Software is created by you. Can you
> show me some sotware project using names with such funky characters?
>
Gour,
one size fits all does not work in real life. For instance, brackets,
spaces, etc. are used in file nam
Is it possible to see a side-by-side difference between the last checkin and
the currently changed file on disk? It would be a great alternative to
fossil diff and fossil gdiff
This would be much like the wiki preview using /doc/ckout/
--
Jos Groot Lipman
___
On Fri, 09 Mar 2012 08:53:21 +0100
Martijn Coppoolse
wrote:
> Why is that a bad practice? Because there's programs (like Fossil)
> that won't let you work with them?
The first three hits on Google with the query "using brackets in filenames"
gives:
http://support.microsoft.com/kb/123577
http
16 matches
Mail list logo
