On Sat, Mar 14, 2015 at 8:07 AM, Graeme Pietersz
wrote:
> The advantage is that anyone can create a Github fork of a public
> project, work on it, and then submit pull requests, without ever being
> given commit access to the original repo. You can have untrusted
> collaborators and review all t
On Sat, Mar 14, 2015 at 12:33 PM, David Mason wrote:
> 1) Fossil's ticket handling is not best-in-class. What are the key
> features that would make it at least competitive? What features does
> it have that are already better than most? (I've never used tickets,
> although the integrated ticket
On Fri, Mar 13, 2015 at 4:08 PM, Graeme Pietersz
wrote:
> I am rather stunned (and a tad concerned) that cars need 100m lines of
> code.
Cars don't really need that much code. A luxury car could have electronic
control modules in a lot of places you might not think of. I know I was
surprised ye
On Fri, Mar 13, 2015 at 4:08 PM, Jan Danielsson
wrote:
> On 13/03/15 20:55, Richard Hipp wrote:
> >> Few organizations have the problem that the full power of Git solves.
> > And yet many organizations voluntarily take on the problems that come
> > with using Git. Weird.
>
>One shouldn't und
On Thu, Mar 12, 2015 at 5:48 AM, Gour wrote:
> Ron W writes:
>
> > Another possibility might be RSS. I recall reading on this list where
> some
> > have set up build servers, such as Jenkins, that monitor the Fossil RSS
> > feed.
>
> I believe that's too co
On Wed, Mar 11, 2015 at 1:49 AM, Graeme Pietersz
wrote:
>
> On 11/03/15 00:45, Ron W wrote:
>>
>> I'm thinking he wants 2 sets of default settings: The existing one (which
>> he perceives as being open source oriented) and another set that are more
>> appropria
On Wed, Mar 11, 2015 at 8:29 AM, Gour wrote:
> Now, I'd like that whenever I commit changes on my local machine and
> push them unto remote server, that the content of 'public' folder gets
> copied/synced to the remote server to the specific directory so that the
> site is automatically refreshed
On Tue, Mar 10, 2015 at 5:54 PM, Joerg Sonnenberger wrote:
>
> Unless "large files" means "larger than 2GB", I don't believe there is
> one. I haven't run into a case where I wanted to use version control
> systems for handling such files yet...
I posted a comment and he replied that his commits
On Tue, Mar 10, 2015 at 4:37 PM, jungle Boogie
wrote:
>
> On 10 March 2015 at 12:15, Ron W wrote:
> > Many issue tracking systems have a GUI, "point and click" query
> > builder/editor. So, SQL use can be mostly avoided.
> >
> > Creating such a query bui
On Tue, Mar 10, 2015 at 4:37 PM, jungle Boogie
wrote:
>
> On 10 March 2015 at 12:15, Ron W wrote:
> > Seems to me that he doesn't realize that Fossil separates the repository
> > from the "working copy". He's expecting "fossil clone" to wor
On Tue, Mar 10, 2015 at 1:58 PM, jungle Boogie
wrote:
> BTW, referring link was this:
> http://www.omiyagames.com/farewell-fossil-version-control/
>
> Author's main complaints about Fossil were:
>
...
> -Author thought you had to run sql each time to list tickets.
>
Many issue tracking systems
On Tue, Mar 10, 2015 at 4:47 AM, Steven Harford
wrote:
> I prefer (2). It's more concise and looks great in each of the examples
> you provided. Therefore, I'm not sure it's worth maintaining both display
> styles in the source code.
>
Also agree
___
f
On Fri, Mar 6, 2015 at 9:11 AM, Tontyna wrote:
> Maybe me and my co-workers aren't exemplars of The Average Fossil User
> (current and future) but typing commands in a shell is not our common
> approach to move or delete files.
> Reference point are files on a harddrive actually belonging to a sp
On Thu, Mar 5, 2015 at 6:57 PM, Andy Goth wrote:
> I haven't encountered any IDEs with ClearCase integration.
>
Well, the point the person demo-ing CC to the group I was with at the time
was that such integration is not necessary. At least not for "mere
developers".
> All my ClearCase experien
On Thu, Mar 5, 2015 at 3:50 PM, Andy Goth wrote:
> Fossil commit is a high-level concept which can't be comfortably
> represented in the OS's filesystem API. Mapping POSIX file writes to
> Fossil commits writes would yield a messy timeline full of intermediate
> versions; temporary files; editor
On Wed, Mar 4, 2015 at 7:05 PM, Warren Young wrote:
>
> You can get the same effect without making yourself nervous with “fossil
> revert”.
This not mentioned in "fossil help revert". It only says "Revert to the
current repository version of FILE" or to specified version.
___
On Wed, Mar 4, 2015 at 5:18 PM, Warren Young wrote:
> Many filesystems and OSes combine file versioning and file management:
>
> https://en.wikipedia.org/wiki/Versioning_file_system
>
> In a sense, VCSes are a way to get such features on top of filesystems
> that lack these abilities.
Fossil
On Wed, Mar 4, 2015 at 5:09 PM, Warren Young wrote:
> On Mar 4, 2015, at 10:24 AM, paul wrote:
> >
> > If fossil mv also moves files on a filesystem, I'd be happy with that,
> so long
> > as I can still use a file browser as I'm doing now.
>
> All other VCSes I’ve used that do one-step mv [*] co
On Tue, Mar 3, 2015 at 6:11 PM, Warren Young wrote:
> Yeah, it’s a bit broken. If file attributes are considered a part of the
> file’s data, and not just local metadata, then:
>
> chmod +x foo
> f ci foo
>
> should result in a checkin even if foo hasn’t otherwise changed.
>
Actually, the "
On Tue, Mar 3, 2015 at 5:47 PM, Warren Young wrote:
> I assume you’re running into this on mixed Windows/Linux systems where
> Windows’ “archive” flag gets translated into a POSIX +x flag? If so, you
> don’t actually want the flag change checked in.
>
Yes. At work, we have a mixed environment.
On Mon, Mar 2, 2015 at 3:14 PM, Matt Welland wrote:
> For example, if I clean up and move things around in a Fossil repo and by
> force of habit do an update before a commit I *lose* some of my clean up
> effort when Fossil (illogically IMHO) brings back the removed files.
>
Where I work, this i
In the check-in Info page, the changes section sometimes has "Execute
permission set" lines. This confuses non-developer people. Is there a way
to filter this out?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org
On Sat, Feb 28, 2015 at 3:40 PM, Andy Bradford
wrote:
> Thus said jungle Boogie on Fri, 27 Feb 2015 12:17:15 -0800:
>
> > Can this be updated to check-in as we are graduating from checkin?
>
> Personally, I prefer checkin without the dash, and definitely for a
> command argument, adding yet
On Sat, Feb 28, 2015 at 1:03 PM, Jungle Boogie
wrote:
> --- www/checkin_names.wiki
> +++ www/checkin_names.wiki
> @@ -159,13 +159,13 @@
> in Universal Coordinated Time (UTC). This tends to work the best for
> distributed projects where participants are scattered around the globe.
> But there
On Thu, Feb 26, 2015 at 3:12 AM, Gaurav M. Bhandarkar wrote:
> OK. The idea that comment on a version is also a tag is new to me. IMO,
> this "fossil specific tag definition" caused this query. When we say "Tags"
> in context of a SCM, people usually think of a label which wraps around a
> specif
On Wed, Feb 25, 2015 at 9:14 PM, Richard Hipp wrote:
> On 2/25/15, Ron W wrote:
>
> > As best I can recall, this is the same behavior I've seen with many other
> > "web apps", including a few I worked on. My work around for this was to
> > include a Javasc
On Wed, Feb 25, 2015 at 7:42 PM, Andy Goth wrote:
>
> Easiest way to demonstrate this problem is to go to:
>
> http://www.fossil-scm.org/index.html/timeline?y=ci
>
> which should initially show Without Files. Select With Files, then
> press the browser's Back button.
>
> At this point files will
On Wed, Feb 25, 2015 at 3:37 AM, Gaurav M. Bhandarkar wrote:
> How is the output lines, eg 16:06 Edit [72114148]: Edit check-in comment.
> (user: drh) [details], related to "most recent tags".
>
For a check-in (or a ticket), "comment" is a tag. The "comment" tag also
has a value, which is the te
On Tue, Feb 24, 2015 at 8:00 PM, Richard Hipp wrote:
> On 2/24/15, Ron W wrote:
> > [Managers] associate dates with deadlines, so version numbers remove
> > a source of panic.
>
> Fair enough. I'll migrate from dates to version numbers in the next
> releas
On Tue, Feb 24, 2015 at 8:03 PM, jungle Boogie
wrote:
> For my day job, version numbers in ANY capacity are out of the
> equation (NOT my choice). The project in question either in trunk/head
> or its in some branch. It pretty much means filing bug reports are
> useless since we can't really iden
On Tue, Feb 24, 2015 at 7:01 PM, Stephan Beal wrote:
> On Tue, Feb 24, 2015 at 9:11 PM, Richard Hipp wrote:
>
>> So it seems like having dates on the download would be more meaningful
>> than having a made-up version number. No? With a date, at least you
>> know about how old the code is. Wha
On Tue, Feb 24, 2015 at 5:16 PM, Richard Hipp wrote:
> It's going to be more complicated than that. The people who want
> ...
> Since this is a major change, I propose that it be deferred until
> Fossil 2.0 (which will likely be the next release).
>
Honestly, it doesn't matter to me. Mr robotan
On Tue, Feb 24, 2015 at 4:47 PM, Andy Goth wrote:
> So just grab the file at this URL:
>
>
> https://www.fossil-scm.org/fossil/tarball/fossil-1.31.tar.gz?uuid=version-1.31
>
> and be happy. The file will have the name you want.
>
> Or replace "1.31" with whichever tagged release you desire.
>
>
On Tue, Feb 24, 2015 at 4:21 PM, Ron W wrote:
>
> Took a quick look at Fossil commits tagged "release", I see tags like
> "version-1.31", "version-1.30", etc. I also see references to SQLite
> versions in the form x.y.z as opposed to a date string.
>
On Tue, Feb 24, 2015 at 3:59 PM, jungle Boogie
wrote:
>
> How have you been updating packages in the past?
>
> All releases are like this:
> 20150223162734
> 20150119112900
> 20140612172556
> 20140127173344
> 2013094349
Took a quick look at Fossil commits tagged "release", I see tags like
"v
On Tue, Feb 24, 2015 at 11:27 AM, Baptiste Daroussin <
baptiste.darous...@gmail.com> wrote:
> 2015-02-24 15:30 GMT+01:00 Richard Hipp :
> > On 2/24/15, robotanarchy wrote:
> >> When downloading file [1], you'll get an archive that has a different
> >> file name than the included folder. The folde
On Mon, Feb 23, 2015 at 11:48 AM, Stephan Beal
wrote:
>
> FWIW, frames were (thank goodness) deprecated in HTML5. iframes are still
> around but work much differently.
>
Been over 10 years since I did any serious web work (was "moonlight" work I
did for a friend). I didn't do the page designs. I
On Thu, Feb 19, 2015 at 2:22 PM, Backe, Martin G
wrote:
> P.s. I’ve never reverted to a previous build, but I assume there’s no
> danger reverting to a recent but older build?
>
Me neither, but I suggest you do a "fossil rebuild" after switch back to
the older version and before doing anything
On Thu, Feb 19, 2015 at 11:33 AM, Fadi Mansour <
fadi.redeemer.mans...@gmail.com> wrote:
> Another question comes to mind.
>
> Could Wiki pages include TH1 commands?
>
I would strongly recommend against this. And if this feature were added,
any repository where it was enabled would need to only a
On Thu, Feb 19, 2015 at 1:31 AM, Fadi Mansour <
fadi.redeemer.mans...@gmail.com> wrote:
> I noticed that using an "_" at the start of a column name makes it
> possible to use wiki strings, which would successfully create links, but
> the problem is that this will break the columnar format of the r
On Wed, Feb 18, 2015 at 4:11 PM, Fadi Mansour <
fadi.redeemer.mans...@gmail.com> wrote:
> I managed to customize the "View Ticket" page to create links from the
> text found in this field, but for reports, there's only the query, and I'm
> not sure if I have access to the logic that is rendering t
On Thu, Feb 12, 2015 at 2:55 PM, Warren Young wrote:
>
> I would still prefer that Fossil self-tune, however. While it is true
> that my formula doesn’t give intuitive p values, it is also true that you
> cannot pick sensible d values for a repository without knowing various
> characteristics abo
On Wed, Feb 11, 2015 at 3:33 PM, Andreas Kupries
wrote:
> AFAIK wiki pages have no parent.
> The various commits to a specific page P are simply _time_ordered_
> under the name of the page.
>
That's my point. The web UI's wiki editor page does not have the ID of the
commit whose content is in th
On Wed, Feb 11, 2015 at 12:19 PM, Richard Hipp wrote:
> The P-card on the Wiki artifact
> (https://www.fossil-scm.org/skin2/doc/trunk/www/fileformat.wiki#wikichng)
> shows the parent(s) of each Wiki commit. This has always been
> recorded.
In Fossil version [3e5ebe2b90], when editing a wiki p
On Wed, Feb 11, 2015 at 10:34 AM, Stephan Beal
wrote:
>
> The infrastructure is there to support merging wikis content just like
> other content, but the logic/code is missing for such handling of wiki
> pages and tickets. Your proposal would add a lot of logic for wikis which
> is already in plac
On Wed, Feb 11, 2015 at 7:54 AM, Richard Hipp wrote:
> Fossil uses file mtimes and sizes to help it detect changes. When
> your tool moves foo to foo.bak, this changes neither the mtime or the
> size. So Fossil fails to detect the change, by default.
But, the "new" foo.bak would have the mtim
On Tue, Feb 10, 2015 at 3:49 PM, Richard Hipp wrote:
> There are two cases:
>
> (1) SHA1 prefixes for human-consumption
>
> The default length of (1) has traditionally be 10 characters, though
> as J notes, that is sometimes extended in order to find a character in
> the range of [a-f]. There ar
On Tue, Feb 10, 2015 at 12:24 PM, Jeff Rogers wrote:
> So what I'm thinking about is instead:
> $ cd ~/dev/
> $ fossil clone http://whatever/projectname ~/fossil_repos/projectname.
> fossil
> $ mkdir projectname
> $ cd projectname
> $ fossil open ~/fossil_repos/projectname.fossil
>
I use a varia
On Mon, Feb 9, 2015 at 4:23 PM, Richard Hipp wrote:
>
> Simpler still is just to scp the repo up to the server.
Last time I tried that (about 1.5 years ago), I had to use an SQL command
to change the ID of the local repository so I could sync it with the clone
on the remote server. since then, I
On Mon, Feb 9, 2015 at 3:57 PM, Richard Hipp wrote:
> The /dev/null device is opened for writing if Fossil finds that its
> file-descriptor 2 is not open when it is launched. (Stunnel4
> sometimes does this.) This is dangerous to run with file-descriptor 2
> not open since it might get opened o
On Mon, Feb 9, 2015 at 3:38 PM, Gour wrote:
> Hmm, what is the correct procedure to clone repository from my desktop
> machine to the *remote* server?
Do you have SSH access to the remote server? If so, I'd say the simplest is
to SSH into the remote server with forwarding from the remote to wha
On Thu, Feb 5, 2015 at 3:25 PM, bch wrote:
> Understood -- I hope I never see an need to run this -- I'd look long,
> and hard before I did. In case anybody is perceiving my interest in
> subverting POSIX locking as implied embracing of subverting POSIX
> locking: I'm am not condoning this.
>
Wh
On Thu, Feb 5, 2015 at 11:09 AM, Abilio Marques wrote:
> Here the current code (missing the capture of the stdout). I send it as a
> patch to the current trunk version (0d1d7f6481).
>
>
> Ideas?
>
I suggest altering the parameter processing to be:
if ( argc == 3 ){
if (fossil_strcmp(argv[1], "N
On Mon, Feb 2, 2015 at 5:35 PM, Warren Young wrote:
> After sending that prior message, I did think of a way to allow retries
> without inconsistency, but it would surely slow Fossil down: there could be
> a mode that turns cloning into a replay of the master repo’s timeline.
>
> That is, every c
On Tue, Jan 27, 2015 at 8:57 AM, Tony Papadimitriou wrote:
> - You cannot split out a project at a later time (wish list). So, you're
> stuck with this arrangement for good.
>
Actually, I think you "sort of" can. If you mark the roots of the projects
you do NOT want to clone as private, then, I
On Tue, Jan 27, 2015 at 9:17 AM, Jim Kalafut wrote:
> - You cannot split out a project at a later time (wish list). So, you're
>> stuck with this arrangement for good.
>>
>
> Is the brand new "bundle" command a potential solution for this? I've only
> read the docs so far, but it seems pretty po
On Sat, Jan 24, 2015 at 4:55 PM, Joerg Sonnenberger wrote:
> On Sat, Jan 24, 2015 at 04:27:55PM -0500, Richard Hipp wrote:
> > I would hope that the local machine knows that it cannot provide IPv6
> > service and that getaddrinfo() should therefore always return an IPv4
> > address. But apparent
On Thu, Jan 22, 2015 at 11:32 PM, Richard Hipp wrote:
> On 1/22/15, Richard Hipp wrote:
> > On 1/22/15, Svyatoslav Mishyn wrote:
>
> > How about if there is a redirect URL for 404 errors on the Setup
>
> That won't work because if the redirect is to another /doc/ page that
> is not found it wil
On Thu, Jan 22, 2015 at 4:15 PM, Richard Hipp wrote:
>
> If there is a custom page for 404 errors, do I still set the Status: to
> 404?
As I recall, the HTTP spec says you should, even if you also supply
(placeholder) content (aka custom 404 page).
However, I don't know if the Redirect header i
On Thu, Jan 22, 2015 at 5:16 AM, Jan Nijtmans
wrote:
> --empty Initialize checkout as being empty, but still
> connected
> with the local repository. If you commit this
> checkout,
> it will become a new "initial" commit in the
> rep
On Wed, Jan 21, 2015 at 12:14 PM, Svyatoslav Mishyn
wrote:
> and demo:
> http://chiselapp.com/user/juef/repository/crux-ports/tree?ci=tip
That does look very nice.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm
On Thu, Jan 15, 2015 at 5:32 PM, Rich Neswold
wrote:
> When I look at the schema of a fossil repo, I see comments like:
>
> -- Do not change any column that begins with tkt_
>
>
> Maybe I misunderstood the meaning. I took it to mean don't change the
> values of these fields. But maybe it means do
On Thu, Jan 15, 2015 at 4:14 PM, Rich Neswold
wrote:
> Maybe the fossil schema can be enhanced by adding triggers that prevent
> UPDATEs from occurring on critical columns.
>
Not sure how much value that would add because all the actual (repository)
data is in the blobs. The ID of each blob is i
On Thu, Jan 15, 2015 at 3:46 PM, Andy Bradford
wrote:
> Thus said "Andy Bradford" on 15 Jan 2015 13:37:24 -0700:
>
> > Or would the sync protocol have to be modified so that the client, on
> > push, receives a copy of any existing artifacts that it is intending
> > to push so that it can compa
On Thu, Jan 15, 2015 at 5:59 AM, Kelly Dean wrote:
> My point remains: Fossil unnecessarily uses an extremely slow hash if
> you're expected to trust the data, and uses one that's too close to being
> broken to warrant trust if you don't trust the data.
Even on 10 year old hardware, Fossil's pe
On Tue, Jan 13, 2015 at 6:24 PM, Kelly Dean wrote:
> Ron W wrote:
> > So, you are asking for an option to enable an automatic, post-commit
> > "fossil diff $@" (where $@ is the list of files just committed)?
>
> Yes. And it needs to compare the contents, not just
On Tue, Jan 13, 2015 at 4:08 PM, Kelly Dean wrote:
> You could say, well, don't use Fossil for storing evidence. But why not?
> An option like ZFS's dedup=verify would solve the problem. Without it,
> Fossil unnecessarily relies on the hash function being secure.
Even if a post-commit "fossil d
On Tue, Jan 13, 2015 at 4:09 PM, Kelly Dean wrote:
> But when committing a new file to a local repository, compare-by-content
> _is_ practical. I'm throwing peanuts at Fossil's failure to even provide an
> option to do that. The user can do it manually: commit, then checkout into
> another workin
On Tue, Jan 13, 2015 at 5:21 AM, Joerg Sonnenberger wrote:
> The much more interesting case is
> getting wrong data send from a 3rd party matching an existing (signed)
> manifest. Comparing content is not an option for that as you don't have
> the original content.
As I understand the Fossil sy
On Sun, Jan 11, 2015 at 11:43 PM, Andy Bradford
wrote:
> I can set up all kind of QoS on my firewall, but most devices don't
> allow one to request random and routine packet loss and actual
> connection resets (e.g. TCP/IP RST packets) as part of the QoS settings.
> ;-)
Just setu
On Mon, Jan 12, 2015 at 7:29 AM, Joerg Sonnenberger wrote:
> On Mon, Jan 12, 2015 at 11:24:13AM +, Kelly Dean wrote:
> > That makes no sense. To avoid common-mode failures in the
> > implementation, you just need a different implementation.
> > You don't need a different algorithm.
>
> It is
On Thu, Jan 8, 2015 at 7:17 PM, Stephan Beal wrote:
> Indeed, the mtime (available directly) and size (available indirectly, via
> a join) are quick checks, but "can one really be certain?" (i'm largely
> playing Devil's Advocate here.)
>
True. Would be worth knowing what git does (and Hg (and m
On Thu, Jan 8, 2015 at 7:01 PM, Stephan Beal wrote:
> On Fri, Jan 9, 2015 at 12:56 AM, Andreas Kupries > wrote:
>>
>> I.e. the command implementation would have to detect the unchanged
>> files on update and skip them.
>>
>
> Which would almost certainly once in a blue moon, as a side-effect of
On Thu, Jan 8, 2015 at 6:45 AM, Ron Aaron wrote:
> Is there any way to have fossil change the ticket resolution to 'fixed'
> when I change the status to 'fixed'?
>
In Administration, in Ticket Config, edit the Edit Ticket page to modify
the TH1 code.
On Tue, Jan 6, 2015 at 12:32 PM, Richard Hipp wrote:
> Expanding this question from fossil-dev to fossil-users after more
> reports of problems.
>
> Apparently some unicode arrow characters (U+2b06, U+2b07, and U+21f3)
> are not displaying properly on many peoples systems, though they work
> fine
On Tue, Jan 6, 2015 at 11:50 AM, Stephan Beal wrote:
> On Tue, Jan 6, 2015 at 5:12 PM, Ron W wrote:
>
>> The "sym-" one not having a value. Strange to me that 2 tags would be
>> used (I would have thought only the "branch" tag), but looks like the
>&g
On Tue, Jan 6, 2015 at 4:04 AM, Stephan Beal wrote:
>
> agreed. AFAIK, branches currently do not use the VALUE part of the tag.
> Perhaps such a description could be set there when making a branch, e.g.:
>
>
> fossil commit -b new-branch -d "branch description" -m "commit message"
>
> That would
On Sat, Jan 3, 2015 at 11:29 PM, Kelly Dean wrote:
> Does Fossil give any warning if you receive a new ticket update with a
> timestamp preceding an update that you yourself created and with a
> conflicting J-card? Then #2 would notice #1's update, even though nobody
> else would. This won't help
On Thu, Dec 18, 2014 at 4:20 PM, Warren Young wrote:
>
> With today’s fast CPUs, Ajax lets us bring back the native client, for all
> practical purposes.
My concern about JS (and Java) is that it is too powerful. And web browsers
are not properly "sand boxing" active content like JS.
I have don
On Thu, Dec 18, 2014 at 2:48 PM, Stephan Beal wrote:
>
> true enough - it's just been a question of effort. We keep the JS to a
> minimum (even moreso because it's tedious to add ;).
>
Perhaps it is good that it is tedious to add/edit the JS?
___
fossil
On Wed, Dec 17, 2014 at 2:10 AM, Scott Robison
wrote:
>
> The thing I dislike about the "strict Microsoft way" is the embedding of
> actual type data into the variable name, so that if you decide to change a
> type later, you have to change all the names. (I realize the above quote is
> not the "s
I think the key thing is that symbol names convey what they are used for.
Dr. Simonyi, nominal originator of "Hungarian Notation", seems to agree in
his paper about naming conventions. Microsoft has republished that paper:
http://msdn.microsoft.com/en-us/library/aa260976%28v=vs.60%29.aspx
My key
On Tue, Dec 16, 2014 at 2:27 PM, Stephan Beal wrote:
>
> (i'm thinking of the sort mechanism we already have in place. i think a
> hidden field might require extending that.)
>
As best I understand, CSS can hide the extra column, just need to make sure
the "sort button" for the age column refers
On Tue, Dec 16, 2014 at 2:11 PM, Stephan Beal wrote:
>
> It also begs the question: how can we sort on that column (using JS) if we
> prettify the times?
>
Maybe have the epoc time as a hidden field? Possibly less overhead that
running the prettify JS in the browser, though that would be an optio
On Mon, Dec 15, 2014 at 2:01 PM, Stephan Beal wrote:
>
> On Mon, Dec 15, 2014 at 7:49 PM, Petr Ferdus wrote:
>>
>> Something similar like taking ls -al of all files in repository,
>> redirecting output to file and versioning that file. Except this would
>> happen automatically on commit or some o
On Wed, Nov 26, 2014 at 5:34 PM, Warren Young wrote:
> On Nov 26, 2014, at 3:07 PM, Ron W wrote:
> > Pull requests are just a notification mechanism that github (possibly)
> first provided as a convenience to github users.
>
> Technically, yes, but when you’re in the GitHub wo
On Wed, Nov 26, 2014 at 4:49 PM, Warren Young wrote:
> Awesome. That will remove Git’s relative advantage of pull requests,
> while making it as easy to use as Subversion.
Pull requests are just a notification mechanism that github (possibly)
first provided as a convenience to github users.
I
On Tue, Nov 25, 2014 at 11:27 AM, Jan Nijtmans
wrote:
> 2014-11-25 16:33 GMT+01:00 Stefan Bellon :
> > If files checked in have CR+LF line endings, then they are correctly
> > put into a local working copy, but when using "fossil cat" or "fossil
> > finfo -p" to retrieve the file (via stdout redi
On Wed, Nov 12, 2014 at 7:05 AM, Peter Spjuth
wrote:
> I'm making a way to attach a fossil revision as a Tcl Virtual File System.
>
> I found it a bit tricky to extract information from fossil and would like
> to
> know if I have missed some command that could make it easier.
>
> For a given revi
On Fri, Nov 7, 2014 at 3:32 PM, Zoltán Kócsi wrote:
> In the Fossil wiki, is there a magic reference that points to the ZIP or
> tar.gz download point of the latest on the trunk?
>
I think a URL like this:
http://fossil-scm.org/index.html/tarball/Fossil-Latest.tar.gz?uuid=trunk
On Fri, Nov 7, 2014 at 2:42 AM, Tony Papadimitriou wrote:
> There is also another possibility. Under Windows, you can use the MKLINK
> command to create a directory junction under your project (each project).
> This way you can keep the tree structure you have, keep a single copy of
> your libra
On Thu, Nov 6, 2014 at 3:35 PM, Joe Prostko wrote:
> On Thu, Nov 6, 2014 at 3:29 PM, Stephan Beal
> wrote:
> > As you probably already know, but here it is for those who don't:
> >
> >
> https://docs.google.com/document/d/13gRSl6-bj3LV-OKgE-BsqvqF33UFYW3oa3A2OJC5QSY/view
>
> I can't view this at
On Tue, Nov 4, 2014 at 2:32 PM, Jan Nijtmans wrote:
>
> Starting with this commit:
> <
> http://fossil-scm.org/index.html/info/7aced530234a04e17a64a3b995a6e12886e5e9b5
> >
> the option --empty was re-used for another purpose than original.
> Apparently a bad idea ;-(
> Now renamed to "--docke
On Tue, Oct 28, 2014 at 5:39 PM, Baruch Burstein
wrote:
>
> On Tue, Oct 28, 2014 at 11:25 PM, Richard Hipp wrote:
>
>> Just be VERY CAREFUL that you don't add an artifact that is also used in
>> some other check-out that you want to keep, because after you shun it will
>> be gone forever.
>>
>
>
On Tue, Oct 28, 2014 at 3:11 PM, B Harder wrote:
> Not a bad idea -- this part of the description:
> < itself) are removed from the repository whenever the repository is
> reconstructed using the "rebuild" command.>>
>
> may roughly be what we're looking for.
Maybe could be as simple as adding
On Tue, Oct 28, 2014 at 2:21 PM, Stephan Beal wrote:
> On Tue, Oct 28, 2014 at 7:14 PM, B Harder wrote:
>>
>> 3) I can't think of anything else...
>>
>
> You will.
>
Perhaps looking at how shunning works would help
___
fossil-users mailing list
fossil
On Tue, Oct 21, 2014 at 5:30 PM, Ron W wrote:
> On Tue, Oct 21, 2014 at 5:32 AM, Baruch Burstein
> wrote:
>>
>> Done. As I said, It is *very* much a work-in-progress.
>>
>
> Looks like a good start. Not as much code as I thought it would require.
>
Baruch,
N
FWIW, in the SVN vs Git community, neither side understands the other
side's rational about even the just tracking branch metadata, let alone
naming branches. The SVN people thought branch IDs were not sufficient. The
Git people say there is no value in tracking branch metadata So much for
trying
On Thu, Oct 23, 2014 at 5:49 PM, Stefan Bellon wrote:
>
> Yes, almost. ;-)
>
> I'm not interested in interactive usage of fossil. We are using fossil
> in a completely automated scenario to track and retrieve generated files
> over time. So, my concern is compatibility and consistency of command
>
In a discussion between a Git user and a user of both Mercurial and Git,
there was a debate of the relative merits of "named branches" vs "bookmark
branches".
Mercurial (and Fossil) supports named branches (Mercurial recently added
support for bookmark branches). Git supports bookmark branches.
W
301 - 400 of 556 matches
Mail list logo
