$ ls -lh ~autobuild/aurae.fossil
-rw-r--r-- 1 autobuild users 11G Sep 15 12:05 /home/autobuild/aurae.fossil
On Fri, 15 Sep 2017, Thomas wrote:
On 2017-09-14 23:43, Richard Hipp wrote:
On 9/14/17, Thomas wrote:
The biggest disadvantage - as my coworkers pointed out -
Le 15/09/2017 à 00:40, Thomas a écrit :
Fossil is a great piece of softare. Its primary strength is certainly
that it is a single executable, easy to set up and easy to run as a CGI.
+1
It’s surprising to see how many features there is in a such small software.
The biggest disadvantage - as
On 15 September 2017 at 15:26, Olivier R. wrote:
> I also wonder what’s the best way to include a one-time patch without giving
> rights to the repository.
one word: bundles
--
Javier
___
fossil-users mailing list
I am not sure the problem is in fossil itself, but don't know from where to
search it.
Anyway, after sync command on one of my repositories, I get the following:
Sync with https://asm32.info/fossil/repo/asmbb
Round-trips: 1 Artifacts sent: 0 received: 0
Sync done, sent: 1930 received: 1817
i have noticed the same thing (i believe the same ip address even) and have
it on my to-look-at list for later. so i'm glad you brought this up. :)
- On Sep 15, 2017, at 3:16 PM, John Found johnfo...@asm32.info wrote:
> I am not sure the problem is in fossil itself, but don't know from where
On 9/15/17, John Found wrote:
> I am not sure the problem is in fossil itself, but don't know from where to
> search it.
> Anyway, after sync command on one of my repositories, I get the following:
>
> Sync with https://asm32.info/fossil/repo/asmbb
> Round-trips: 1
On 9/15/17, Richard Hipp wrote:
>
> Perhaps Apache is setting the REMOTE_ADDR environment variable. What
> does https://asm32.info/fossil/repo/asmbb/test_env show for the
> administrator? (You have that page turned off for anonymous, so I
> cannot see it.)
Nevermind - the
just for completeness ... i verified that i am seeing the same address
during a commit:
Autosync: https://redacted
Round-trips: 1 Artifacts sent: 0 received: 0
Pull done, sent: 390 received: 994 ip: 2.0.1.187
New_Version: 906246b7cd7e5fec91c69502981582bdbfc0a89e
Autosync: https://redacted
On 9/15/17, Dewey Hylton wrote:
> just for completeness ... i verified that i am seeing the same address
> during a commit:
>
> Autosync: https://redacted
> Round-trips: 1 Artifacts sent: 0 received: 0
> Pull done, sent: 390 received: 994 ip: 2.0.1.187
> New_Version:
Sadly, I do not know how to do such a thing as I am not a developer. The
concept is not foreign to me as I have a bit of experience with python, so I'll
give it a shot starting with Google. Pointers to get me on the right track
would be welcomed.
> On Sep 15, 2017, at 3:58 PM, Richard Hipp
> On Sep 14, 2017, at 11:12 PM, Johan Kuuse wrote:
>
> I would like to have a stronger argument against rebasing, preferrably with
> an example.
It’s been hashed over here on the mailing list many times before. Just search
the archives for “git rebase”.
The short argument I
El 16 sept. 2017 0:39, "Warren Young" escribió:
> On Sep 14, 2017, at 11:12 PM, Johan Kuuse wrote:
>
> I would like to have a stronger argument against rebasing, preferrably
with an example.
It’s been hashed over here on the mailing list many times before.
12 matches
Mail list logo