> I won't fail to defend general anti-nym opinion or guidance
d-oh, s/defend/defend against/
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscr
>> grarpamp
>> the various good uses for nyms.
> cpgh...@cordula.ws
> I hope you realize whom you're trying to lecture here!
> Joerg Wunsch is a highly appreciated long-time FreeBSD contributor
Of course. No one here has any question as to anyone's FreeBSD
participation. That would be silly :) I
On 11/18/12 01:31, Konstantin Belousov wrote:
On Sat, Nov 17, 2012 at 11:05:40PM -0800, Perry Hutchison wrote:
[trimmed some of the lists]
Chris Rees wrote:
... git doesn't work with our workflow.
I'm sure the workflow itself is documented somewhere, but is
there a good writeup of _how_ git
On Sun, Nov 18, 2012 at 1:57 AM, Garrett Wollman wrote:
>> the various good uses for nyms.
>
> There are no such uses on the FreeBSD mailing-lists; if you wish for
> anyone to pay attention to you, then use a real name. Otherwise,
> FOAD.
>
> -GAWollman
It appears you have not reviewed the maili
On Sun, Nov 18, 2012 at 02:37:11PM +0100, Dimitry Andric wrote:
> On 2012-11-16 23:04, Navdeep Parhar wrote:
> >On 11/16/12 13:49, Roman Divacky wrote:
> >>Yes, it does that. iirc so that you can have things like
> >>
> >>void foo(int cond) {
> >> if (cond) {
> >> static int i = 7;
> >> } e
On Nov 18, 2012, at 5:37 AM, Dimitry Andric wrote:
> On 2012-11-16 23:04, Navdeep Parhar wrote:
>> On 11/16/12 13:49, Roman Divacky wrote:
>>> Yes, it does that. iirc so that you can have things like
>>>
>>> void foo(int cond) {
>>> if (cond) {
>>> static int i = 7;
>>> } else {
>>>
on 18/11/2012 16:04 Adrian Chadd said the following:
> On 18 November 2012 02:48, Andriy Gapon wrote:
>
>> What you describe is not a workflow issue, but a local development
>> environment(s) setup issue.
>
> Which is a workflow issue.
Well, this is what I understand as workflow:
google://git w
Why not make few such places? This will be harder to compromise
simultenously two or more.
Regards, Alexander Yerenkow
18.11.2012 16:13 пользователь "Aldis Berjoza" написал:
>
> 18.11.2012, 16:10, "Alexander Yerenkow" :
> > How about each commit will make a "tweet"? I'm sure
> > twitter could ar
On 18 November 2012 14:04, Adrian Chadd wrote:
> On 18 November 2012 02:48, Andriy Gapon wrote:
>
>> What you describe is not a workflow issue, but a local development
>> environment(s) setup issue.
>
> Which is a workflow issue.
>
> I mean, we could bang heads on semantics for hours on end, or w
On 18 November 2012 09:09, Alexander Yerenkow wrote:
> Integrity could be provided by storing some kind of commit ( each, and
> additionally each 1000nd full) checksums (even for svn) somewhere on
> readonly format.
Google "Merkle Tree" for a method of verifying a log.
--
Eitan Adler
18.11.2012, 16:10, "Alexander Yerenkow" :
> How about each commit will make a "tweet"? I'm sure
> twitter could arrange create-records-only (no edit) acount for such project
> as FreeBSD is.
> This isn't so hard to make, and it's so social :)
And you would trust twitter?
--
Aldis Berjoza
FreeBS
Integrity could be provided by storing some kind of commit ( each, and
additionally each 1000nd full) checksums (even for svn) somewhere on
readonly format. How about each commit will make a "tweet"? I'm sure
twitter could arrange create-records-only (no edit) acount for such project
as FreeBSD is
On 18 November 2012 02:48, Andriy Gapon wrote:
> What you describe is not a workflow issue, but a local development
> environment(s) setup issue.
Which is a workflow issue.
I mean, we could bang heads on semantics for hours on end, or we can
realise that git isn't a magic bullet for FreeBSD dev
On 2012-11-16 23:04, Navdeep Parhar wrote:
On 11/16/12 13:49, Roman Divacky wrote:
Yes, it does that. iirc so that you can have things like
void foo(int cond) {
if (cond) {
static int i = 7;
} else {
static int i = 8;
}
}
working correctly.
It's not appending the .n everyw
On 16 Nov 2012, at 14:04, Navdeep Parhar wrote:
> On 11/16/12 13:49, Roman Divacky wrote:
>> Yes, it does that. iirc so that you can have things like
>>
>> void foo(int cond) {
>> if (cond) {
>>static int i = 7;
>> } else {
>>static int i = 8;
>> }
>> }
>>
>> working correctly.
>
>
on 18/11/2012 10:15 Adrian Chadd said the following:
> On 17 November 2012 23:31, Konstantin Belousov wrote:
>
>> Git would work well with our workflow. It supports the centralized
>> repository model, which the project employs right now.
>
> It may work with your workflow, but it doesn't work w
Hello, Adrian.
You wrote 18 ноября 2012 г., 8:55:54:
AC> There's a git repository. It's public. You can look at what goes into
AC> the FreeBSD git clone to get your assurance that things aren't being
AC> snuck in. People are using it, right now.
But commits in this repo aren't signed by developer
On 17 Nov 2012, at 23:05, Perry Hutchison wrote:
> [trimmed some of the lists]
>
> Chris Rees wrote:
>> ... git doesn't work with our workflow.
>
> I'm sure the workflow itself is documented somewhere, but is
> there a good writeup of _how_ git doesn't work with it, e.g. what
> capabilit{y,ies
On 17 November 2012 23:31, Konstantin Belousov wrote:
> Git would work well with our workflow. It supports the centralized
> repository model, which the project employs right now.
It may work with your workflow, but it doesn't work with mine. :-)
Right now the source tree isn't very good at bui
19 matches
Mail list logo
