On Fri, Aug 2, 2013 at 11:55 AM, Richard Hipp wrote:
> On Fri, Aug 2, 2013 at 11:51 AM, Benedikt Ahrens
> wrote:
>
Hello,
>>
>> I am having trouble with a fossil repository containing many binary files.
>>
>> The fossil version is the one packaged in Debian Wheezy:
>>
>> $ fossil version
>> Th
Hi,
Alternatively, you could
accept X-Forwarded-For by default when the remote address is the local
host. That should take care of the most common setup.
Yes, when X-Forwarded-For is not the localhost, and Remote_Address is
the localhost. Most probably this is not IP forgery in this case. It
On Sat, Aug 3, 2013 at 6:16 PM, Maxim Khitrov wrote:
> >
> > Your patch would allow clients to forge their IP address by injecting an
> > X-Forwarded-For header in the HTTP request. Fossil has no way of
> knowing if
> > the X-Forwarded-For comes from a trusted proxy or a malicious client.
>
> Wh
On Sat, Aug 3, 2013 at 5:59 PM, Richard Hipp wrote:
>
>
> On Sat, Aug 3, 2013 at 4:59 PM, Maxim Khitrov wrote:
>>
>> On Sat, Aug 3, 2013 at 4:52 PM, reverse
>> wrote:
>> > Hi,
>> >
>> > I also had some problems behind proxy. Solved those by having one more
>> > Apache instance just for Fossil de
On Sat, Aug 3, 2013 at 4:59 PM, Maxim Khitrov wrote:
> On Sat, Aug 3, 2013 at 4:52 PM, reverse
> wrote:
> > Hi,
> >
> > I also had some problems behind proxy. Solved those by having one more
> > Apache instance just for Fossil deployment.
> >
> > Please consider taking value of HTTP_FORWARDED_RE
On 3 Aug 2013 14:58:01 -0600
"Andy Bradford"
wrote:
> Sometimes it's a matter of simply convincing enough people about why
> the current mechanism is *wrong* (offering to write the code also
> helps).
Heh, check "The case for Markdown (yes, I rtfm)" thread from 2009. ;)
Sincerely,
Gour
--
On Sat, Aug 3, 2013 at 4:52 PM, reverse wrote:
> Hi,
>
> I also had some problems behind proxy. Solved those by having one more
> Apache instance just for Fossil deployment.
>
> Please consider taking value of HTTP_FORWARDED_REQUEST_URI (if present)
> instead of PATH_INFO, and of X-Forwarded-For i
Thus said Gour on Sat, 03 Aug 2013 22:05:04 +0200:
> > This is not to say that things shouldn't change in Fossil regarding
> > how branches work.
>
> Well, recalling how much opposition was against using some more
> 'standard' markup (ala markdown) and how long it took to implement it,
> I
Hi,
I also had some problems behind proxy. Solved those by having one more
Apache instance just for Fossil deployment.
Please consider taking value of HTTP_FORWARDED_REQUEST_URI (if present)
instead of PATH_INFO, and of X-Forwarded-For instead of REMOTE_ADDRESS.
-Alexandru Toth
On 3 Aug 2013 13:50:46 -0600
"Andy Bradford"
wrote:
> I distinctly recall reading a description of the differences
> between ``branches'' in Fossil and other DVCS (specifically Git),
> which likely explains why things are the way they are:
Yeah, this explains things: "So to a first approxim
Thus said Gour on Sat, 03 Aug 2013 21:25:01 +0200:
> Moreover, iirc, there was also another request to be able to push
> distinct branches which also, afaict, is not implemented.
>
> Both features are something which one takes for granted in every other
> DVCS (bzr, darcs, git, hg...)
I dist
On Sat, 3 Aug 2013 09:49:43 -0700
B Harder wrote:
> Sorry, on mobile and time constrained, but do private branches
> address this in any way?
I don't know if something has changed, but previousy the only way to get
rid of private branches was via:
fossil scrub --private
but, iirc, there was no
B Harder wrote:
Sorry, on mobile and time constrained, but do private branches address
this in any way?
I get a lot of mileage out of them, FWIW. When working on the Fossil
codebase, I do all my experimental work (which turns out to be most of
it...) in private branches. Then when I have
Thus said Stephan Beal on Sat, 03 Aug 2013 19:48:07 +0200:
> Ah, right, that's the www interface and you want the CLI... that
> one's a bit more difficult, so i won't be patching that tonight.
> The timeline is probably the most complicated single piece of
> functionality in t
On Sat, Aug 3, 2013 at 6:44 PM, Andy Bradford <
amb-sendok-1378140242.poacifknllljkhgok...@bradfords.org> wrote:
> Thus said Stephan Beal on Sat, 03 Aug 2013 18:23:46 +0200:
>
> > http://fossil-scm.org/index.html/info/73135ec22a
>
> Wow that was quick!
>
Only because it was easy to do and i'm be
On Sat, Aug 3, 2013 at 6:49 PM, B Harder wrote:
> Sorry, on mobile and time constrained, but do private branches address
> this in any way?
>
No idea - i have never used private branches.
--
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
_
On Aug 3, 2013 7:09 AM, "Stephan Beal" wrote:
>
> On Sat, Aug 3, 2013 at 3:36 PM, Gour wrote:
>>
>> a) Search feature seems to be addressed, right?
>
>
> Yes.
>
>>
>> b) uncomit - ability to simply uncommit last commit which I'd do while
>> still staying in my local repo and prior to pushing any
Thus said Stephan Beal on Sat, 03 Aug 2013 18:23:46 +0200:
> http://fossil-scm.org/index.html/info/73135ec22a
Wow that was quick!
I suppose an alternate approach could have been to modify ``fossil
timeline'' to accept a TAG to restrict its search to just those
artifacts with the
On Sat, Aug 3, 2013 at 6:23 PM, Stephan Beal wrote:
> Sure, it does!
>
> http://fossil-scm.org/index.html/info/73135ec22a
>
Caveat: when using the --raw flag the ordering is undefined (those elements
have no time information, apparently), so the limit is not all that useful
there.
--
- ste
On Sat, Aug 3, 2013 at 5:55 PM, Andy Bradford wrote:
> fossil tag find experimental
>
> It doesn't appear to have a way to limit the number of results to
> return, so it isn't exactly the same.
>
Sure, it does!
http://fossil-scm.org/index.html/info/73135ec22a
--
- stephan beal
http:
Thus said Isaac Jurado on Tue, 28 May 2013 17:34:49 +0200:
> > At http://www.fossil-scm.org/fossil/timeline?n=200&r=experimental it
> > looks like there are a dozen or more "experimental" branches
> > currently in the Fossil tree.
>
> That is very interesting. How do you achieve the same
On Sat, Aug 3, 2013 at 3:36 PM, Gour wrote:
> a) Search feature seems to be addressed, right?
>
Yes.
> b) uncomit - ability to simply uncommit last commit which I'd do while
> still staying in my local repo and prior to pushing any changesets to
> the wilderness. It's simply tedious not to be
Hello,
Due to some missing features I had to move away from Fossil to git, but
I still appreciate many of the design choices in Fossil.
There are certain TODO items and considering I'm not closely following
Fossil development, I'd just like to make a brief check what's going on.
I can see that n
23 matches
Mail list logo
