> Le 14 juin 2018 à 22:23, Thomas a écrit :
>
>> Mailing list messages are easily filtered.
>> I have one mailbox for each mailing list I subscribe to, and I read through
>> the messages in list order, which makes it easy to mentally switch gears
>> from one project to the next.
>
> Most peopl
Le 16/06/2018 à 17:05, Eduardo Morras a écrit :
I partially disagree. If you allow anonymous people to pull / commit /
merge data to your 'central repository', you can get easily spammed. If
I pull-request 100 images of 10MB your system will go down. Multiply it
by several 'funny guys' on more t
Another issue with bundles: "push requests" derived from local private branches.
It may be not only the receiver of a "push request" to decide to
import only the final "accumulated patch", without all the detailed
"commit-by-commit" history.
It may also be the submitter to decide to keep the deve
On Sat, Jun 16, 2018 at 05:05:48PM +0200, Eduardo Morras wrote:
>
> I partially disagree. If you allow anonymous people to pull / commit /
> merge data to your 'central repository', you can get easily spammed.
> If I pull-request 100 images of 10MB your system will go down.
> Multiply it by severa
On Fri, Jun 15, 2018 at 04:39:20PM -0400, Richard Hipp wrote:
> On 6/15/18, Chad Perrin wrote:
> >
> > This would not technically be a "pull request". It would be a "merge
> > request".
>
> Good point. It should not be called "pull-request" as pulling does
> not come into play.
>
> On the othe
On 6/16/18, Zack Scholl wrote:
> Hi,
>
> First of all I love fossil - thank you for all the work that goes into
> making it.
>
> I just tried the feature to make my repository private (Admin ->
> Security-Audit). Now my repository is "Completely PRIVATE" which is great,
> but I'm thinking I'd lik
Hi,
First of all I love fossil - thank you for all the work that goes into
making it.
I just tried the feature to make my repository private (Admin ->
Security-Audit). Now my repository is "Completely PRIVATE" which is great,
but I'm thinking I'd like to make it public once I finish coding.
I d
On Sat, Jun 16, 2018 at 3:07 AM, Stephan Beal wrote:
> On Sat, Jun 16, 2018 at 12:46 AM Stephan Beal
> wrote:
>
>> i will write a longer response when i'm back on the PC, but short version:
>>
>> - refactoring to a lib is a huge effort.
>> ...
>> More details upcoming about that first point in t
>> ... it's possible to introduce unwanted contents (and random
>> control artifacts) ...
I can foresee another attack that could be used to inject malicious
control artifacts into the repository (depending on the bundle
implementation). The attacker creates a delta control artifact
referencin
More thoughts:
> fossil merge --bundle BUNDLE ?--cherrypick|--backout CHECK-IN?
* BUNDLE could be a disk file, or something like "bundle:ID" to refer
to a bundle submitted via "push request", and queued in a separate
repository db table.
* If the current check-out is different from the root of t
On Fri, 15 Jun 2018 13:35:13 -0400
Richard Hipp wrote:
> On 6/15/18, David Mason wrote:
> > I heartily agree with this... A flag to allow a person (including
> > Anonymous) to make a commit that would automatically go into a new
> > branch like "Patch-1" (each one incrementing the branch number)
fossil submit
Steve
On 16 Jun 2018, 9:30 PM +0800, Tony Papadimitriou , wrote:
> -Original Message-
> From: Richard Hipp
>
> > Other ideas for what to name this (hypothetical and unimplemented) command:
> >
> > fossil contribute
> > fossil bequest
> > fossil bestow
> > fossil proffer
>
>
-Original Message-
From: Richard Hipp
Other ideas for what to name this (hypothetical and unimplemented) command:
fossil contribute
fossil bequest
fossil bestow
fossil proffer
Some more ideas (in random order):
fossil chip-in (shortest possible is ch)
fossil enqueue (shorte
Eduard:
> I have opened registration on Hydra. Feel free to try it out at
> [ https://hydra.ecd.space/ ], and give me your feedback.
Roy Keene:
> Is ChiselApp not serious enough for you ?
(Quotes unconnected.)
I think both ChiselApp and Hydra are very nice, and technically solid
projects (and
On Sat, Jun 16, 2018 at 12:07 PM Stephan Beal wrote:
> libfossil had essentially all of the core-most functionality
> running (documented, too)
>
http://fossil.wanderinghorse.net/repos/libfossil/doxygen/
Ah, those were the days... (i actually _miss_ documenting software.)
--
- stephan be
> Let me decide whether the bundle is committed "step-by-step"
> ... or "all-at-once" ...
I think this is what I'm looking for:
fossil merge --bundle BUNDLE ?--cherrypick|--backout CHECK-IN?
> But I would like to have some more flexibility and control when
> "applying" (or importing) bundles by
On Sat, Jun 16, 2018 at 12:46 AM Stephan Beal wrote:
> i will write a longer response when i'm back on the PC, but short version:
>
> - refactoring to a lib is a huge effort.
> ...
> More details upcoming about that first point in the morning.
>
So...
http://fossil.wanderinghorse.net/r/libfossi
Fossil bundles are a great feature, and may be useful to implement
pull (or "push") requests.
But I would like to have some more flexibility and control when
"applying" (or importing) bundles by third parties:
* Let me decide where the bundle is committed, be it directly on trunk
instead of on a
18 matches
Mail list logo
