Thus said org.fossil-scm.fossil-us...@io7m.com on Sat, 09 Aug 2014 16:48:04
-:
> I don't suppose there's any way to make fossil hit a given URI
> whenever the current repository receives artifacts?
You might be able to use the commit hooks for this:
http://fossil-scm.org/index.html/
Thus said Stephan Beal on Sat, 09 Aug 2014 20:31:48 +0200:
> fossil zip trunk my.zip
Yes, that will work just perfectly fine for what I need, thanks.
Andy
--
TAI64 timestamp: 400053e6e144
___
fossil-users mailing list
fossil-users@lists.fossil-s
On 2014-08-09 12:48, org.fossil-scm.fossil-us...@io7m.com wrote:
I don't suppose there's any way to make fossil hit a given URI whenever
the current repository receives artifacts?
Could the recently discussed RSS feature help, at least to provide
notifications of updates on the public side?
Andy Bradford wrote:
> Does Fossil have an option that exports a particular revision of the
> repository similar to how CVS export works? CVS export will export
> either HEAD or an explicit revision to a named directory without all the
> CVS control directories/files in the export.
>
>
Thanks to both you and Andy for your explanations.
fossil zip seems like a great solution for what I need.
Now, if there was a matching ‘unzip’ to do the hypothetical unzipping and serve
the files as is, it would be even greater! (The name ‘unzip’ only as a mental
opposite to ‘zip’, not to sug
On Sat, Aug 9, 2014 at 8:30 PM, Andy Bradford
wrote:
> Does Fossil have an option that exports a particular revision of the
> repository similar to how CVS export works? CVS export will export
> either HEAD or an explicit revision to a named directory without all the
> CVS control direc
Hello,
Does Fossil have an option that exports a particular revision of the
repository similar to how CVS export works? CVS export will export
either HEAD or an explicit revision to a named directory without all the
CVS control directories/files in the export.
As far as I can tell, the
On Sat, Aug 9, 2014 at 8:26 PM, Andy Bradford
wrote:
> It looks like fossil ls does not honor the -R option---perhaps it
> should?
>
Mine does ;)
[stephan@host:~/cvs/fossil/libfossil/s2]$ f-ls -R ../../cwal.fsl | head
File list from manifest version 'trunk' [e4088e92c12b] (RID 5551)...
T
Thus said "Tony Papadimitriou" on Sat, 09 Aug 2014 20:58:41 +0300:
> * it doesn't seem to be the actual reason as I ran your query on my
> various fossils, and many of them return zero rows or very few rows
> compared to the number of opens it went through so far.
If you close the repos
On Sat, Aug 9, 2014 at 7:58 PM, Tony Papadimitriou wrote:
> * this seems kind of pointless, given I can open the same repo in multiple
> locations at the same time. Are you sure you're not referring to the
> separate _FOSSIL_ database, instead, or some special operation that changes
> that tabl
Hmm, I may not know the internals of how fossil works, but I have these
observations:
* this seems kind of pointless, given I can open the same repo in multiple
locations at the same time. Are you sure you're not referring to the
separate _FOSSIL_ database, instead, or some special operation th
Thus said "Tony Papadimitriou" on Sat, 09 Aug 2014 20:01:30 +0300:
> Every time I open a fossil repo, even if I simply open it to just get
> a copy of the files in some directory, I end up with a 'touched' repo
> file, as if some 'write' operation has occurred in the database.
Every time foss
Hi,
Every time I open a fossil repo, even if I simply open it to just get a copy
of the files in some directory, I end up with a 'touched' repo file, as if
some 'write' operation has occurred in the database. And a binary compare
of before and after shows that some bytes actually change. How
On 2014-08-09T10:23:35 -0600
"Andy Bradford"
wrote:
>
> If none of your public-facing repositories accept commits, wiki edits,
> or tickets, or in otherwords are completely read-only, you could stage
> the public-facing repositories on your local system and then use rsync
> to copy them to
Thus said Steve Bennett on Fri, 08 Aug 2014 15:55:51 +1000:
> Are you sure you just changed /home to 711?
> Worked OK for me:
I did some more testing and despite the errors, it does actually build
jimsh0:
$ ls -l autosetup/jimsh0
ls: autosetup/jimsh0: No such file or directory
$ ./autosetup/f
Thus said org.fossil-scm.fossil-us...@io7m.com on Sat, 09 Aug 2014 09:46:37
-:
> I'm using what I believe is probably a common setup: I have a server
> on my private network here containing the "canonical" repositories for
> all my projects. I have clones of these repositories on all mach
Thus said org.fossil-scm.fossil-us...@io7m.com on Sat, 09 Aug 2014 11:39:31
-:
> The problem there is that I want it to tell me when a sync fails, but
> I don't want to hear "sync succeeded" over and over.
cron will only email if there is output, so you can suppress stdout and
leave stder
Using rsync, make and some smart log file processing using logpro I was
able to bidirectionally sync over 250 fossils every two minutes between
three sites. It worked very well for two years and then we switched to all
sites using ssh. If details on this would be useful let me know and I'll
write i
On 2014-08-09T13:43:32 +0200
Stephan Beal wrote:
> On Sat, Aug 9, 2014 at 1:39 PM,
> wrote:
>
> > The problem there is that I want it to tell me when a sync fails, but I
> > don't want to hear "sync succeeded" over and over. Essentially, I only
> > want output if the process in question returns
On Sat, Aug 9, 2014 at 1:39 PM,
wrote:
> The problem there is that I want it to tell me when a sync fails, but I
> don't want to hear "sync succeeded" over and over. Essentially, I only
> want output if the process in question returns a non-zero exit code.
> The program I ended up writing to perf
On 2014-08-09T13:25:21 +0200
Stephan Beal wrote:
> You can suppress that: simply redirect all output: >/dev/null 2>&1
> cron only mails if the program generates output. Better yet, redirect it
> all to a running log file:
>
> >> /path/to/log 2>&1
The problem there is that I want it to tell me w
On Sat, Aug 9, 2014 at 11:46 AM,
wrote:
> became unwieldly (due to the number of repositories and the way cron
> would send me email every time fossil said anything),
You can suppress that: simply redirect all output: >/dev/null 2>&1
cron only mails if the program generates output. Better yet,
On Sat, Aug 09, 2014 at 10:45:14AM +, org.fossil-scm.fossil-us...@io7m.com
wrote:
> I've not used master mode before. From what I can make out from the
> ssh_config manual page, this causes ssh to open a single long-running
> connection to the server which is re-used by anything connecting to
On 2014-08-09T12:14:46 +0200
Joerg Sonnenberger wrote:
> On Sat, Aug 09, 2014 at 09:46:37AM +,
> org.fossil-scm.fossil-us...@io7m.com wrote:
> > If you open too many ssh connections in too short a time, they'll
> > throttle and close connections.
>
> Have you tried using Master mode? Try run
On Sat, Aug 09, 2014 at 09:46:37AM +, org.fossil-scm.fossil-us...@io7m.com
wrote:
> If you open too many ssh connections in too short a time, they'll
> throttle and close connections.
Have you tried using Master mode? Try running:
ssh -v -MN -o ControlPath=/tmp/socket remote
and in a sepa
'Lo.
First of all, because this doesn't get said enough: Thanks for fossil!
Been a happy user for three years now, and I love the approach taken to
UI simplicity and the focus on reliability and integrity. I have no
idea how I coped before having an integrated ticket system.
However, one aspect o
26 matches
Mail list logo
